I want to get number of times the issue made some transaction.
Suppose my workflow has Ready to Retest--> Reopen. Now if 1 issues is marked as ready to retest but it was reopened, again after fixing that issue was marked ready to retest but again tester reopens the issue.
Considering above scenario I want to know how many times the issue was reopened.(need its count)
Thanks in Advance.
I don't think it's possible without any add-ons. For example with Script Runner plugin you can define a scenario like this:
It is the best possible solution that I can think of on Cloud.
I'm afraid there is no automatic way to get that number. You can check issues one by one, you can see the transitions made on the transition tab but I'm sure you already know that and it is not an ideal solution. I'm sorry I couldn't be more help.
that has the functionalty of your needs. You can check that one. As Elifcan mentioned above, its not easly possible to find transtion count without searching history tab.
Create calculated custom fields that evaluate a Java expression to compute the value of the field. Can be of type Number, Date or String.
Create custom fields that will hold the date/time or the name of the caller of any transition in your workflow.
Additional JQL functions you can use in your issue filters.
The Jira Misc Custom Fields plugin's objective is to provide several new types of custom fields for use in custom Jira workflows as well as useful JQL functions.
Included custom fields:
Included JQL function:
Do you have Jira Misc Workflow Extensions plugin in your Cloud instance? If yes,
Now every time the ticket is reopened the "Reopened Count" field value increments by 1.
Hope this helps,
Found another simple way to do this:
Set up a rule on your project to listen for a specific issue transition (either using JQL condition or the transition options, then add an Edit issue action.
Select the field you want (My Customfield) to increment and use the following value:
This will increase the value every time the issue goes into that status.
Found this from @Nick Menere
Hi @Veronica Mapes , I was trying to implement your solution and I continue to get this error: Error while parsing additional fields. Not valid JSON.
Would you mind looking at my screenshot and tell me where I'm going wrong? I know it's user error I just don't know what I'm failing to do.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events