...
| # | Title | Detail | Reporter | Notes | |||
|---|---|---|---|---|---|---|---|
| 1 | 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. | A solution is to have an admin for each team to handle their own projects but the problem with having too many admins is global mistakes can happen if not careful. An admin can change global settings by mistake which will then affect everyone using the same JIRA instance. Or maybe have a team dedicated in managing JIRA Cloud as other companies have done. | ||||
| 2 | Default Screens being affected | Today while importing csv file of issues from another cloud instance, Vincent had to create custom fields which is done during the import process. Even though the project issue types were associated with project specific screen schemes, those project specific screen schemes contained multiple screens. One of them containing a default screen which then got edited with the new custom fields. To avoid this in the future, admins will have to make sure the project screen schemes are not associated with default screens. |  |
| |||
| 3 |