jira | simple jira command line client in Go | Command Line Interface library

If you're running a recent version of Jira, there was a GDPR-related change that causes all newly-created users to have a key starting with JIRAUSER instead of their username. Users can also be anonymized through this feature.

You can get a mapping of JIRAUSER keys to usernames through the JIRA API's Get User endpoint -- not sure where to look in the database for this mapping yet.

The first part (prefix) is the Project Key representing a project/collection where all similar issues are stored (in this case, ASAPSD may stand for ASAP Service Desk:-). There are certainly more projects in every Jira instance. Some other projects are intended to track different activities.

You can search for any issues using the search function (available also via REST API).

First, log in to the Jira and try to search for the issues manually by yourself - in Issue Navigator (via Issues top menu bar). Here you'll find that you can search all issues via Basic (Project is ASAPSD) or Advanced search (project = ASAPSD). This advanced search is called JQL (Jira Query Language).

You can then use this JQL in your REST API search method: https://docs.atlassian.com/software/jira/docs/api/REST/latest/#api/2/search-search

GET https://jira.yourdomain.com/rest/api/2/search?jql=project%3DASAPSD

• The output lists only limited number of issues (usually 50) - to get more issues, you need to increase the limit (maxResults param) or paginate (startAt param) over next results.
• Using expand and fields params you can alter the output to get more/less information.
• There two types of Jira instances - on-premise Server/Data Center and Cloud one. REST API and usage might slightly differ.
• Alternatively, you can get CSV export. When you search for issues in the Issue Navigator, there's an option to export results to CSV. Save this URL and you can request it in your script via GET.

As I'm aware there is no such built in functionality, but you can build a bot to do this.

Basically you write an application which listens to a JIRA webhook which is configured to trigger if an issue is updated.
The bot will then trigger the actions for you in Gitlab. Depending on your setup there it could set approvals ( incase you are using the deployment branch model ) or trigger the deployment pipeline after it is already merged by the code owner. This is done using the GitlabAPIs
Finally you can update the issue in JIRA using the API with the status of the deployment

ActiveMQ Artemis has no default connection limit. I just wrote a quick test based on this which uses the Paho 1.2.5 MQTT client. It spun up 500 concurrent connections using both normal TCP and WebSockets. The test finished in less than 20 seconds with no errors. I'm just running this test on my laptop.

I noticed that your journal-buffer-timeout is 700000 which seems quite high which means you have a very low write speed of 1.43 writes per millisecond (i.e. a slow disk). The journal-buffer-timeout that is calculated, for example, on my laptop is 4000 which translates into a write-speed of 250 which is significantly faster than yours. My laptop is nothing special, but it does have an SSD. That said, SSDs are pretty common. If this low write-speed is indicative of the overall performance of your VM it may simply be too weak to handle the load you want. To be clear, this value isn't related directly to MQTT connections. It's just something I noticed while reviewing your configuration that may be indirect evidence of your issue.

The journal-buffer-timeout value is calculated and configured automatically when the instance is created. You can re-calculate this value later and configure it manually using the bin/artemis perf-journal command.

Ultimately, your issue looks environmental to me. I recommend you inspect your VM and network. TCP dumps may be useful to see perhaps how/why the connection is being reset. Thread dumps from the server during the time of the trouble would also be worth inspecting.

I found solution - https://confluence.atlassian.com/adminjiraserver/configuring-renderers-938847270.html#Configuringrenderers-autocompleterenderer

We should set Autocomplete renderer for fix version field.

You can use

From the synopsis of the command module:

The command(s) will not be processed through the shell, so variables like $HOSTNAME and operations like "*", "<", ">", "|", ";" and "&" will not work. Use the ansible.builtin.shell module if you need these features.

So, your issue is the fact that the command module is not expanding the wildcard *, as you expect it, you should be using the shell module instead:

Setting jiraResp in the method callback will trigger a re-render and since you are making the method call in the render method itself, it will repeat the call, hence the loop.

You need to use useEffect:

You could write a javascript function to iterate and process each issue in your response. For example: