THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
JIRA
...
JIRA contains the entire project history, but as the project has matured our use of JIRA has not kept up. This page proposes some changes to the structure of our JIRA project, to capture more information, simplify the data entry and nudge people towards more complete and accurate data entry. This will better allow us to measure release quality over time and identify when Cassandra is ready for (or due a) release.
Summary
- Removal of...
- Issues types: Wish and Test
- Fields: Labels, Reviewer, Environment, Reproduced In, Docs Text, Due Date, Epic Link, External Issue Id, External Issue URL, Flags, Sprint, Time Tracking
- Modify fields: Priority, Component
- Add Fields: Complexity, Severity, Bug Category, Feature Category, Discovered By, Feature, Impacts, Test and Documentation Plan, Platform
- Feature,
Removals
To simplify the maintenance of JIRA, it would help to remove any unnecessary concepts. Mostly these are concepts we do not use in practice, except very spottily (so as to make them useless).
...
Field | Reason | Migration |
|---|---|---|
Labels | See detailed discussion below | |
Reviewer | Replaced by Reviewers | Populate empty Reviewers fields with contents of Reviewer |
Environment | Use is very patchy, noisy, and seemingly of little value over a comment if the extra content is useful | Propose new multi-select 'Platform' field with curated option list, in detail below. We can insert a comment with the environment text for any tickets containing it presently. |
Reproduced In | Use is very patchy; seems to offer little practical value above 'Since Version' or a comment. | |
Docs Text | Unused |
|
Due Date | Unused |
|
Epic Link | Unused |
|
External Issue ID | Unused |
|
External Issue URL | Unused |
|
Flags | Unused |
|
Sprint | Unused |
|
Time Tracking | Unused |
|
...