...
- Identify bugs and/or missing features in Atlassian Suite so that we can come up with solutions.
Feedback
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 | | Jira Legacy |
|---|
| server | JIRA (yaleits.atlassian.net) |
|---|
| serverId | 0ff96486-f711-332c-a18e-be3fd600929c |
|---|
| key | JS-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. | | 
Image Removed |
| 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 | | Jira Legacy |
|---|
| server | JIRA (yaleits.atlassian.net) |
|---|
| serverId | 0ff96486-f711-332c-a18e-be3fd600929c |
|---|
| key | JS-3 |
|---|
|
|
| 3 | Permissions | Diagram of permission schemes | https://confluence.atlassian.com/adminjiraserver071/configuring-permissions-802592437.html | Kate | | Jira Legacy |
|---|
| server | JIRA (yaleits.atlassian.net) |
|---|
| serverId | 0ff96486-f711-332c-a18e-be3fd600929c |
|---|
| key | JS-4 |
|---|
|
|
| 4 | 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 | | Jira Legacy |
|---|
| server | JIRA (yaleits.atlassian.net) |
|---|
| serverId | 0ff96486-f711-332c-a18e-be3fd600929c |
|---|
| key | JS-5 |
|---|
|
|
| 5 | Feature | Create Project with shared configuration | This allows a project to share workflows, issue schemes, etc with an existing project. This is useful to remove some of the tedious work admins need to do for creating projects that will share the same configuration. But this also means if a project needs to change configuration, they will have to be very careful if they don't want the other project to be affected. | Donal | | Jira Legacy |
|---|
| server | JIRA (yaleits.atlassian.net) |
|---|
| serverId | 0ff96486-f711-332c-a18e-be3fd600929c |
|---|
| key | JS-6 |
|---|
|
|
Not Doing