Alexey Matveev Expert

Why do you not use one workflow for your 20 projects? In this case you would make a change only once.

Do you mean linked to a specific incident? Then you can use linkedIssues(issueKey, CaseSensitiveLinkType) If you want to see all histories linked to a specific project then you could make a JQL like this project=projectKey and issuetype=history

Yes, you need to populate the resolution field to achieve a strike. You can either add a screen with the Resolution field to a transition (if you want to set a resolution manually) or you can add a post-function which will set a resolution automatically. You can create a custom screen and add the Resolution field there.…

If you want to add a resolve issue screen to a transtion you need to add a screen with Resolution field to the transition. Or you can add a post-function to the transition which will set a resolution for the issue automatically.

Do you mean that you want to use Swimlanes for grouping issues in the board? You can group only by Epics and Stories. If your histories are subtask issue types then you can group by Strories. If histories are connected to incidents by a link then you can not do it.

Hello, It would be something like this SELECT user_id, display_name, updated_date last_login, attribute_value login_count FROM cwd_user a, cwd_user_attributes b where attribute_name = 'login.count' and a.id = b.user_id

Yes, it is called worflow properties. You can read more here https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html

Hello, If you are using Jira Cloud then you could have a look at a plugin called Who is looking for Jira Cloud https://marketplace.atlassian.com/plugins/whoslooking-connect/cloud/overview I do not know if the plugin fulfils your requirements, but It is not that difficult to write such a plugin for Jira Cloud or Jira…

Hello, You can use Insight plugin https://marketplace.atlassian.com/plugins/com.riadalabs.jira.plugins.insight/server/overview

That is right you need to log them as different issue types. Their prefix will be the same (the key of the project)

Yes, you are right. If all issues are in the same project than you can differentiate them by issue types. Or you could move them to different projects.

What do you want to return? There will be an array of full user names not a singe full user name. Do you want to return an array?

Hello, I guess "completed issue" is defined by the most right column in the scrum board not by resolution. Have a look here: https://confluence.atlassian.com/jirakb/how-does-jira-agile-decide-when-an-issue-is-complete-for-reporting-purposes-779158578.html

It would be something like this actorRole.getUsers().each{it.getDisplayName()} 

Hello, Did you try to see the logs? Do you have any error there?

You can select your team's issues by using JQL query. For example assignee in (name1, name2, name3)

The normal Jira Service Desk one. But now I undertand that you use a plugin. My solution will not fit.

Hello, You can find such a code here https://community.atlassian.com/t5/Jira-questions/How-can-I-increment-a-custom-field-value-in-a-post-function/qaq-p/74690

I managed to download the fields only in HTML format.

When you add a web item try to fill the weight field with 1000. The weight field influences the order.

Yes, I can just repeat Nic's words: No harm in asking if you can't find something! It is ok if you ask. No problem with it.

Time for first response and time for resolution are the SLA CustomField Type. They are defined in the SLA configuration. Have a look at the configuration of the SLA and try to understand why it is empy. The issues you are looking at must be in the same project where the SLA Custom fields are defined.

You can not create a hierarchy out of the Components field. We are talking about the Components field, are not we?

Hello, An SLA metric is just a custom field of the SLA CustomField Type. That is why you can go to the Issue Navigator and add an SLA custom field as a column. You will be able to see it.

Hello, The Components field is just a field. You can not move it but you can assign a new value to the field. What do you mean by moving components?

You can not do it out of the box. You would need an add-on like Power Scripts or Adaptivist Scriptrunner. If you had Adaptivist Scriptrunner you could use the following JQL function issueFunction in subtasksOf(" fixVersion = \"19 Sep 2017\"") and issuetype = "Testing" If you had Power Scripts you could write your own JQL…

Hello, What do you mean by particular subtask? What kind of subtask do you want to be shown?

do you install on Windows?

Hello, You need to use Jira REST API to create an issue in jira. Kindly have a look at the following doc. You can find an example there: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-post

Hello, The error means that you do not have the Edit issues permisson for the issues. If the issues are from differrent pojects then you need this permission for all project. Kindly read more about permission sheme here: https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html