We have a workflow setup that updating status in Bug will also update the status in linked issue(e.g Epic or story). This is setup using JMWE. For example when a bug is changed to "New" to "Inprogress", the linked issue(Epic or story) also will change to New to inprogress.
But in filter results, the status of linked issue is showing wrong status e.g in issue it is actually in In progress state, but in filter it still showing in Status "New".
When I do Jira full re-indexing, then filter results shows correct status as in issue. But problem is there are many projects having extracting reports using filters at specific intervals(1day,weekly/hourly report) and i cant do re-indexing all the time.
In both Bug and Linked issue(Epic or Story), the postfunctions "Re-index an issue to keep indexes in sync with the database" is present before to "Fire a Generic Event that can be processed by Listeners".
Could you please help in resolving the problem
Yes. I am using Transition Related issues Post function. My order of postfunction tasks are
1. Set issue status to the linked status of the destination workflow step.
2. Add a comment to an issue if one is entered during a transition.
3. Update change history for an issue and store the issue in the database.
4. On each issue linked to the current issue through the relates to link type , the first applicable transition from this list will be triggered:(Transition related issues Postfunction)
5. Re-index an issue to keep indexes in sync with the database.
6. Fire a Generic Event event that can be processed by the listener.
The workflow is setup in a way that moving Status of Bug from "In Progress" to "Close" will also change status of linked issue from "In Progress" to "Close" automatically.
If I move the transition issue post function to bottom, both Bug status and linked issue status will update as desired?
Yes, of course. The position of the post function doesn't change anything for the current issue. And I'm not even sure it'll fix your problem - it could be coming from something else. But the Transition Relayed Issues post function should always be at the bottom.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
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