I'm trying to set up a structure that has epics at the top level, which collapses into the issues linked to the epics by epic link, which would then collapse into the issues that are linked to them by a composition link.
The issue that we're having with this is that the synchronizers update each other with their own data, so thei'll break each other's links.
We considered having the synchronizers run with a user that has structure edit permission but no issue edit permissions to make a read only structure that will still display the data, but even that isn't working, depending on which synchroniser ran last between the 2 the issues keep getting arranged differently according to which synchronizer ran last between the 2.
Anyone have an idea as to how this can be pulled off?
Hi, do you use Links synchronizers and/or Epics synchronizer? Also, which version of Structure?
When using multiple Links synchronizers on one structure, they must be separated with the "child query / parent query" parameters. For example, first synchronizer would have "parent JQL" equal to "type = Epic" and second synchronizer will have "parent JQL" equal to "type != Epic". (As an example, you can think of other separation and "child JQL" parameter too.)
If you use Agile synchronizer for Epics, and Links synchronizer for other issues, I'd advise to again set up Links synchronizer with the additional scope restrictions.
Does that help?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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