Proposed Changes to JIRA
Demo Project: Sakai JIRA
Issue Types
The issues have been modified to have 3 "top level" choices and a variety of sub tasks. This provides simplicity at first glance (ie issue reporters) with the further issue types available to project teams.
Issue Type |
Description |
|---|---|
Bug |
Defect in the software |
Task |
Discreet action that needs to be taken. ie generate artifacts for 2.6.0 release |
Enhancement |
Backend or user facing enhancements to the software that introduce new functionality |
Design (subtask) |
Design associated with active enhancement work |
Coding (subtask) |
Coding associated with active enhancement work |
Bug/Defect (subtask) |
Bug Defect associated with active enhancement work |
Testing (subtask) |
Testing associated with active enhancement work. This can be regression, performance, unit, ect . . |
Sub-task (subtask) |
Discreet action that needs to be taken resulting from bug, task or enhancement work. |
New Permission (subtask) |
Permission changes associated with active enhancement or bug fixing work |
Conversion Script (subtask) |
Conversion script associated with active enhancement or bug fixing work |
Create Issue: The create issue page has been pared down to include the minimal amount of information required.
Old |
New |
Rationale for Change |
|---|---|---|
Project (Read Only) |
Project (Read Only) |
|
Issue Type (Read Only) |
Issue Type (Read Only) |
|
Summary |
Summary |
|
Priority |
Priority |
|
Components |
Components |
|
Affects Version |
Affects Version |
|
Fix Version |
(removed) |
Project team should be setting this. |
Assignee |
(removed) |
Project lead/team should be setting this. |
Reporter |
(removed) |
Most of the time this isn't going to be changed. |
Environment |
Environment |
|
Description |
Description |
|
Attachment |
Attachment |
|
Original Estimate |
(removed) |
Reporter does not always have background to provide this info |
Security Level |
Security Level |
|
Security Issue |
Security Issue |
|
Test Plan |
(removed) |
Is being added as tab on edit screen |
2.4.x Status |
(removed) |
Analysis of function still underway |
2.5.x Status |
(removed) |
Analysis of function still underway |
2.6.x Status |
(removed) |
Analysis of function still underway |
Edit Issue: The Edit issue page has been reorganized
Old |
New |
Rationale for Change |
|---|---|---|
Project (Read Only) |
|
Not necessary |
Issue Type (Read Only) |
Issue Type |
editable |
Summary |
Summary |
Moved above Issue Type |
Priority |
Priority |
|
Components |
Components |
|
Affects Version |
Affects Version |
|
Fix Version |
|
Project team should be setting this. |
Assignee |
|
Project lead/team should be setting this. |
Reporter |
|
Most of the |
Environment |
|
|
Description |
|
|
Attachment |
|
|
Original Estimate |
|
|
Security Level |
|
|
Security Issue |
|
|
Test Plan |
|
|
2.4.x Status |
|
|
2.5.x Status |
|
|
2.6.x Status |
|
|
Assumptions
- Project teams are responsible for reviewing all bug reports and analyzing which versions are affected (this applies to the supported version
- Affects Version
- set by reporter initially, reviewed by project team (see above)
- Component Leads are responsible for assigning out JIRA tickets
- Trunk is a valid fix version.
- When we release a version, any issue that is open will have the affects version updated to include the released version.
- Issues will not be closed until *all* activity is finished
Open Questions
- How should the 2.4.x, 2.5.x and 2.6.x drop downs be handled in this brave new world?
- Change workflow for different issues types?
- Need further information on testing tab?
- Need to talk with someone at Atlassian to see about best practices
- link issue dropdown contains numerous duplicate options. FIX
- Addition of project type categorization?
- r&d
- incubator
- active
- maintenance
Implementation Notes
- Be sure that custom fields are associated with the project you want them to display in!
- Default issue type will be Bugs
- Affects version is custom