...
| # | Type | Title | Detail | Reporter | Notes |
|---|---|---|---|---|---|
| 1 | Issue/Bug | JIRA Management Issue | Managing JIRA becomes tedious and complicated as the user base grows. Different teams/projects requires different project customizations. Current admins will not have the time to manage more complex projects and the creation of new projects that requires customized permissions, notifications, workflows, issue type schemes. | Donal |
|
| 2 | Feature | Components | helpful for organizing projects: https://confluence.atlassian.com/adminjiraserver071/managing-components-802592503.html This is useful for organizing larger projects into smaller chunks (i.e. for Canvas Dev we have multiple projects) | Kate |
|
| 3 | Permissions | Diagram of permission schemes | https://confluence.atlassian.com/adminjiraserver071/configuring-permissions-802592437.html | Kate | |
| 4 | Something | Make Guides/Checklists for Global Admins | Set up best practice guides and checklists to ensure that global admins can create what they need without affecting other groups using the JIRA/Confluence instance. | Donal | |
| 5 | What to do | Clean up of inactive workflows, issue schemes, etc | Should we ever do clean ups? Is there a limit on how many workflows, issue schemes, permission schemes, etc? Should we remove inactive ones or duplicate ones - teams might want to go back to them and change them. If we never clean up what would happen in the long term? Should we be sharing these things since a team might change them for their project one day and another team that associated their project to it will also get affected. | Donal |