Issue workflow for one issue type ("Blueprint)" creates CLONES (Using Groovy/Script runner), using issue type of "Specification" and "Test Plan".
When I resolve this issue using the appropriate transition (And JIRA default "Resolve" screen)
Now when I OPEN the issue and view status, it shows:
HOWEVER... when I view this issue in a list (such as "Issues" screen in project, or "Assigned to me" on dashboard... it shows:
Status: Approved (This is the workflow status I was in before I clicked "Resolve issue")
Additionally- This is causing problems for my VALIDATE functions in the other issues, since they're set up to confirm that Blueprint issue status is RESOLVED before they can be moved to Resolved/Closed statuses.
About my "Clone issue and links" post functions:
After reviewing this question: https://answers.atlassian.com/questions/109548/issue-navigator-showing-erroneous-status-and-resolution I have noticed that deleting the links to ALL cloned issues is the only way to get the resolution and status to display correctly in the issue lists!
(The problem description sounds very close to mine too)
The answer on the aforementioned question link is not clear - if the script is "not indexing the new/updated issues", how do I fix this? Is there a bug in the groovy script runner? I have followed all instructions and reviewed all groovy documentation for "Clone an issue and links" post function. I can't figure out where I'm going wrong.
It is very important that we are able to properly resolve issues while retaining the links to our "Clones" in the project. Please help!
Moved the "Clone issue and links" post function that is on the "Resolve" transition for "Blueprint.
After thinking about reindexing and issue links, I thought the "Test Plan" cloned issue may be the culprit, since it is executed upon "Resolve" transition for the Blueprint issue.
I moved this issue down in the Post Function list - it is now between "Reindex" and "Fire event" JIRA default post functions. This fixed the status problem for the Blueprint issue.
Not quite sure I understand this answer... have you solved the problem? Did you see the info note in the docs: https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Clonesanissueandlinks ?
Due to indexing changes in JIRA 5.1, this post-function should be placed immediately after the function: Re-index an issue to keep indexes in sync with the database. If you don't do this, the parent issue will not be indexed correctly.
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG