To make things more flexible for project administators, we're looking to use project roles. I've hit a snag however, in that the default membership only applies on projects created after the defaults were set.
This does make sense to a degree, however if I want to make a bulk change there doesn't appear to be an easy way to do this.
Any suggestions? Aside from manually changing all the projects by hand (time consuming and error prone).
We've come up with the below sql query, however it's not quite right yet (it doesn't appear to correct filter out devs, although it does when you include roletypeparameter in the select statement). The below filters by project catagory.
SELECT DISTINCT p.id FROM project p INNER JOIN nodeassociation na ON p.id = na.source_node_id LEFT OUTER JOIN projectroleactor pra ON p.id = pra.PID WHERE na.sink_node_id = 10101 AND na.sink_node_entity = 'ProjectCategory' AND pra.roletypeparameter != 'Project Devs';
The project category filter does work, so I think there is something wrong with the joins (still wrapping my head around them).
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