We are facinng re-indexing issues in the Jira version 5.2.5. The problem is as follows.
1. We have a Postfunction(Customised), which copies certain values from Parent CR to Child CR(Child CR is given as the input field, in the closed transition screen), when Parent CR is Closed.
2. When we query for the issues which are "not closed", along with the issues which are in "not closed" state, the Parent CR also shows up in the issue Navigator, with the status as "Open". But when we navigate to the parent CR, the CR has the status "Closed".
By Moving the PostFunction just above the built-in re-index function. The issue is solved. Yes, the child issues get Updated. The Log does not show anything, which gives a hint.
In the Previous Version(Jira 5.0.4), this customised Post function was placed at top position, same configuration change was made use, in this version too.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs