-
Suggestion
-
Resolution: Duplicate
-
None
-
10
-
The problem: Manually set up each new Team-Managed project (formerly Nex-Gen projects) from scratch
Currently, we have to manually set up each new Next Gen project's board columns, issue types, fields, and permissions. This takes time to start from scratch each time, and it's easy to forget to customize something.
Solution idea: Share project settings across projects or duplicate projects
Share Next Gen project settings across projects - or duplicate a project to keep its settings.
Maybe share custom issue types and statuses across projects for better reporting across projects, as well. For example, a custom issue type called "Design" could be re-used across multiple projects, rather than creating duplicate "Design" issue types for each.
- duplicates
-
- Future Consideration
- is duplicated by
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
[JRACLOUD-72818] team-managed / Next Gen: Share settings across projects or duplicate projects
I believe this issue is a duplicate of JRACLOUD-78729 – Ability to clone team-managed projects
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!
So my org could most definitely use this functionality and would love to see this implemented asap! Where this comes into play for us is we have multiple external vendors that need to access only 1 or 2 projects out of the hundreds we have, to do this we setup a group for said users and gave that group access to only the specific projects, but this setting is not relevant in NextGen projects so the users were able to see ~15 additional projects than they should have. However, we didnt initially want to resolve this issue by simply making those projects 'private' as they needed to be open for internal business purposes...
Ultimately the solution we landed on was to make every NextGen project private and create a single user group that all current + new internal users are automatically added to. Then 1-by-1 within each of those projects we added that group called 'jira-software-users' to the 'Access' section, and made sure to exclude the external vendors we were attempting to block.
While this did indeed address our needs, it's a convoluted solution at best. Also because there's currently no way to make this config as described a template within NextGen projects not only did we have to manually it to all of our existing projects, we're also forced to constantly rebuild it on each and every new project created going forward. So if you will please seriously consider this request it would be much appreciated.
As per this comment I am closing this ticket.
If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.