Dear ALM guys,
we are using Structure Add-on (version 4.2.0) with our Jira Server (version 7.4.2) and it is a real great help. Most questions around Structure we could get solved by ourselves by either reading the documentation or by playing around a bit.
But currently we are stuck with something, where we do not know, if it is an issue with Structure itself or if we just have some setting mistake.
We have several structure views available and usually each Jira issue is contained in at least one of these structures. By default the structure settings for the issue page are "Auto-switch to" enabled and "Structure with the displayed issue" is selected. So we would expect, that, when opening an issue, the structure view would automatically select the structure, this issue belongs to.
However, this does not work. The behavior for me (being Jira Administrator) and any of my team members is always, that the structure on the issue page is the last one opened by the user. So this is the behavior as if "Auto-switch" was DISabled.
What are we doing wrong?
The issue is most probably due to the structure being built by generators. Only issues added manually (or by synchronizers) can be detected by auto-switch. The reason for this is that to find a structure with the issue all generators in the system would have to be run on a regular basis, which would create a huge performance overhead.
If however, the structures with manually added issues are not being selected, could you contact us via email@example.com with additional details?
Sorry for inconvenience,
ALM Works Support
sorry for not coming back sooner, but unfortunately I didn't get a notification that there was a reply to my question.
Now, yes, the structure/s in question are in fact created with automation and so this is seemingly "by design".
However we have modified a bit our way of working and currently only use one single main generic and automated structure in the whole company and have set this as the global default one. So usually everything now works fine.
Thank you very much for your efforts.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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