We experience strange behaviour that issues disappear after about 10-15 seconds from both the Greenhopper Epic and the Structure plugin.
Scenario 1: In Greenhopper, drag an issue from the backlog into an Epic or create an issue from the Epic directly. The Epic field is correctly presented on the issue, but this disappears after 10-15 seconds. Epic field in the issue gets cleared.
Scenario 2: Add an issue to a structure page using Add to Structure on the issue main page. The issue is shown on the Structure page, but disappears from the page after about 10-15 seconds. The issue is not linked to the Structure page anymore.
Seems this is not related to the plugins, but to JIRA. Should we consider upgrading to a later version of JIRA as a first step? Still the issue is unexplained.
(also replied by email)
It’s likely a synchronizer at work. For example, a Filter synchronizer in “remove” mode may remove non-matching issues from the structure. To check who removes the issue, open that structure in the Structure Board, and use History bar to see who did remove the issue. Details here: https://wiki.almworks.com/x/HIKF
To check which synchronizers are installed, use Manage Structure page, “Settings” link in the Sync With… column. The descriptions of synchronizers are here: https://wiki.almworks.com/x/kwBg
My best guess is that you have at least two synchronizers installed: a Filter synchronizer and GreenHopper synchronizer. So what happens is:
If that seems to be the cause, the workaround is to recreate the Filter synchronizer but don't enable "Remove" mode.
It appears that regardless of the direction, if Remove mode for a Filter synchronizer is set, then it not only removes from the structure, but also removes the epic link. Remove should only remove from the structure, if the Direction is set JIRA Agile -> Structure.
I only want stories in my structure that are a certain status - so without the remove, I have to manually monitor these stories and manually remove them from the structure; otherwise, they will be unlinked from their Epics.
We have multiple structures to slice and dice the data because the Summation and the Progress columns do not update based on a filter. For example, I can't see the sum of the story points for issues "in Progress" if I filter those issues within the structure because the sum of the story points shows ALL issues and sub-issues and does not subtotal based on the filter. I wouldn't need a filter synchronizer if this functionality existed.
If the JIRA Agile synchronizer adds issues to the structure that are under the epics, then what functionality does the filter synchronizer provide to me? None, in this case because I want to filter on the status of my stories.
Not sure if this is a bug or a feature enhancement request.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs