I was running into a problem where the resolution date in Jira Align was not being set.
Now that I added a new post function to correct the workflow, the resolution date is correctly being set for issues moving to the 'Accepted' state.
However, this newly added post function does not apply to previous issues that are already in the 'Accepted' state.
I was wondering if there was a way to bulk update all issues so that they are applied with the newly added post function and all of their resolution dates will be populated with the date that they moved to the 'Accepted' state.
Can I assume that previously there was no resolution being applied when issues transitioned to the "Accepted" status?
If that's the case, the best suggestion I have would be using scriptrunner to iterate through your issues that are in status "Accepted" and have no resolution. For each of them, get the date that they transitioned to "Accepted" and set the resolution date to that value.
Yes, that is correct. Previously, no resolution was being applied when issues moved to the "Accepted" status.
Thanks! That seems like a reasonable solution. However, I am not familiar with scriptrunner and I do not think my company has access to it. Also, how would I determine what date they moved to "Accepted"? Is there a date better than the issue's last updated date? That could potentially work, but it would assume that nothing in the issue has been updated since being "Accepted".
I would still argue that anything is better than nothing, but I also would say last updated date isn't completely reliable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can view a ticket's "Activity" at the bottom of the page - it's the same section where you normally view Comments.
In my example here, the ticket transitioned to the "Done" status on 4/28 at 12:23 PM
You could see this information presented a different way in the "History" tab, which is right beside the "Activity" one
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.