nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filter query results is showing different status than actual issue status

Tamil

Hi,

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

Accepted answers

All comments

David Fischer

Hi Tamil,

Are you using a Transition Related Issues post function for that? If so, did you move it to the bottom of the list?

Regards

David

Tamil

Hello David,

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.

David Fischer

Can you try moving the post function to the bottom?

Tamil

Moving the "Transition related issues PF" to bottom will it update the current ticket(say for e.g Bug is current ticket and linked issues is Task/story). will it affect/update status of both current and linked issues?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

filter

workflow

issue-link

addon-com.innovalog.jmwe.jira-misc-workflow-extensions

status