#1 The advantage of running the synchronizers as "self" is that the generic filters can be used and the structure for each user does not have to be created to manage issues/tasks pertaining to specific user.
#2 Second question I have is.
Could you build structure from a set of structures set up as a building block or from various disciplines? Kind of a hierarchical structure. The idea behind this is that I can manage various disciplines of a project development in individual structures and then use the individual structures to build a system wide structure.
If it is not supported right now, which is it appears to be, are there plans to implement such features in the future?
I believe this unlocks a serious potential for using Structure for day to day tasks and manage small-to-big pieces of a complex project/team management.
1. That isn't currently possible - Structure synchronizers run on the server under the credentials of the user who created them.
From JIRA's point of view, the currentUser() for a synchronizer is always the user that created it, regardless of who is currently logged in to JIRA in browser sessions.
2. Yes, this is a fairly standard practice - In your Master Structure (structure of structures), you have meta-issues to contain each component Structure's issues, and Filter Synchronizers to pull them in.
Then you need Links Synchronizers running on every Structure so that you can synchronize their hierarchies to the Master Structure.
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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