[
https://issues.apache.org/jira/browse/COMDEV-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16759034#comment-16759034
]
Vuthysean commented on COMDEV-303:
--
JIRA Concepts - Issues
JIRA tracks issues, which can be bugs, feature requests, or any other tasks you
want to track.
Each issue has a variety of associated information including:
the issue typea summarya description of the issuethe project which the issue
belongs tocomponents within a project which are associated with this
issueversions of the project which are affected by this issueversions of the
project which will resolve the issuethe environment in which it occursa
priority for being fixedan assigned developer to work on the taska reporter -
the user who entered the issue into the systemthe current status of the issuea
full history log of all field changes that have occurreda comment trail added
by usersif the issue is resolved - the resolutionIssue Types
JIRA can be used to track many different types of issues. The currently defined
issue types are listed below. In addition, you can add more in the
administration section.
For Regular Issues BugA problem which impairs or prevents the functions of the
product. Epic New FeatureA new feature of the product, which has yet to be
developed. Story ImprovementAn improvement or enhancement to an existing
feature or task. Wish Task SVN->GIT Migration New TLP New TLP - Common Tasks
Blog - New Blog Request Blogs - New Blog User Account Request Blogs - Access to
Existing Blog New Bugzilla Project SVN->GIT Mirroring IT HelpFor general IT
problems and questions. Created by JIRA Service Desk. AccessFor new system
accounts or passwords. Created by JIRA Service Desk. Choose from below ... RTC
TCK Challenge Dependency upgradeUpgrading a dependency to a newer version
Request Question Temp Brainstorming UmbrellaAn overarching type made of
sub-tasks Requirement Comment Planned WorkAssigned specifically to Contractors
by the VP Infra or or other VP/ Board Member. Outage Project Office Hours
Proposal GitBox Request Dependency New Confluence Wiki New Git Repo Github
Integration Sub-task
Priority Levels
An issue has a priority level which indicates its importance. The currently
defined priorities are listed below. In addition, you can add more priority
levels in the administration section.
BlockerBlocks development and/or testing work, production could not run
CriticalCrashes, loss of data, severe memory leak. Major Minor Trivial
StatusesStatus Categories
Helps identify where an issue is in its lifecycle.
Issues move from To Do to In Progress when work starts on them, and later move
to Done when all work is complete.
Done
Represents anything for which work has been completed" style="background:
rgb(20, 137, 44); border: 1px solid rgb(20, 137, 44); border-radius: 3px;
color: rgb(255, 255, 255); display: inline-block; font-size: 11px; font-weight:
bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center;
text-decoration: none; text-transform: uppercase; vertical-align: text-bottom;
white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width:
12em; word-wrap: normal; word-break: normal;">DONE" style="background: rgb(255,
211, 81); border: 1px solid rgb(255, 211, 81); border-radius: 3px; color:
rgb(89, 67, 0); display: inline-block; font-size: 11px; font-weight: bold;
line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center;
text-decoration: none; text-transform: uppercase; vertical-align: text-bottom;
white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width:
12em; word-wrap: normal; word-break: normal;">IN PROGRESS" style="background:
rgb(204, 204, 204); border: 1px solid rgb(204, 204, 204); border-radius: 3px;
color: rgb(51, 51, 51); display: inline-block; font-size: 11px; font-weight:
bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center;
text-decoration: none; text-transform: uppercase; vertical-align: text-bottom;
white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width:
12em; word-wrap: normal; word-break: normal;">NO CATEGORY" style="background:
rgb(74, 103, 133); border: 1px solid rgb(74, 103, 133); border-radius: 3px;
color: rgb(255, 255, 255); display: inline-block; font-size: 11px; font-weight:
bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center;
text-decoration: none; text-transform: uppercase; vertical-align: text-bottom;
white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width:
12em; word-wrap: normal; word-break: normal;">TO DO
Issue Statuses
Each issue has a status, which indicates the stage of the issue. In the default
workflow, issues start as being Open, progressing to In Progress, Resolved and
then Closed. Other workflows may have other status transitions.
Open
The issue is open and ready for the assignee to start work
