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 type
- a summary
- a description of the issue
- the project which the issue belongs to
- components within a project which are associated with this issue
- versions of the project which are affected by this issue
- versions of the project which will resolve the issue
- the environment in which it occurs
- a priority for being fixed
- an assigned developer to work on the task
- a reporter - the user who entered the issue into the system
- the current status of the issue
- a full history log of all field changes that have occurred
- a comment trail added by users
- if the issue is resolved - the resolution
Issue 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
- Change
- Created by Jira Service Desk.
- Service Request with Approvals
- For requests that require approval. Created by Jira Service Desk
- Support
- For customer support issues. Created by Jira Service Desk.
- Incident
- For system outages or incidents. Created by Jira Service Desk.
- Service Request
- Created by Jira Service Desk.
- IT Help
- For general IT problems and questions. Created by Jira Service Desk.
- Problem
- Track underlying causes of incidents. Created by Jira Service Desk.
- Bug
- A problem which impairs or prevents the functions of the product.
- Epic
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
- Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
- New Feature
- A new feature of the product, which has yet to be developed.
- Task
- A task that needs to be done.
- Improvement
- An improvement or enhancement to an existing feature or task.
- In Progress
- Access Request
- Requests for access to Couchbase systems
- Anything regarding email systems. Including client issues, distribution list changes, email bounce-backs and spam
- Redirect
- SEO
- New Hire
- All new hire tickets and requests will go here.
- Page
- A new page either standalone or within a series of pages must be added
- Purchasing
- Ticket for purchasing hardware/software.
- Computer Refresh
- Issue for computer refresh, repair, or service
- Project
- CBIT related issue type - IT Projects
- Escalation Request
- Customer or Field Team escalation request for existing customer issue
- Webinar
- Lookbook
- Blocked
- Version Port
- Minimal ticket to represent porting a fix from a primary ticket to a different product version.
- Paid Media
- Reporting
- Database / Operational
- Needs Approval
- Task needs approval by Assignee
- List Upload
- Review
- Task needs review by Assignee
For Sub-Task Issues
- Account Approval [TEST]
- Approval needed
- Technical task
- A technical task.
- Sub-task
- The sub-task of the issue
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.
- Test Blocker
- QE-related tests can't proceed
- Blocker
- Blocks development and/or testing work, production could not run.
- Critical
- Crashes, loss of data, severe memory leak.
- Major
- Major loss of function.
- Minor
- Minor loss of function, or other problem where easy workaround is present.
- Trivial
- Cosmetic problem like misspelt words or misaligned text.
- High
- Serious problem that could block progress.
- Medium
- Has the protential to affect progress.
- Low
- Minor problems or easily worked around.
- Highest
- This problem will block progress.
- Lowest
- Trivial problem with little or no impact on progress.
Statuses
Status 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
- In Progress
-
Represents anything in the process of being worked on
- No Category
-
A category is yet to be set for this status
- To Do
-
Represents anything new
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 on it.
- In Progress
- This issue is being actively worked on at the moment by the assignee.
- Reopened
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- Resolved
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- Closed
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- Need Info
- To Do
- Done
- New
- Status indicating that an issue is new and hasn't been evaluated by the development team yet.
- Backlog
- In the backlog, planned to work on.
- Current
- Reviewable
- CB Validation
- Sign Off
- In Review
- Blocked
- Purchasing
- Ticket for purchasing hardware/software
- Approved
- QA (Accttwo)
- Copywriting
- Drafted
- Design
- Staged (Prod)
- Live
- Research
- Waiting for Stakeholder Approval
- Canceled
- Completed
- Pending
- Work in progress
- Under Review
- Cancelled
- Rejected
- Declined
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for support
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for customer
- This was auto-generated by Jira Service Desk during workflow import
- Escalated
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for approval
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting CAB approval
- This was auto-generated by Jira Service Desk during workflow import
- Planning
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting implementation
- This was auto-generated by Jira Service Desk during workflow import
- Implementing
- This was auto-generated by Jira Service Desk during workflow import
- Peer review / change manager approval
- This was auto-generated by Jira Service Desk during workflow import
- Under investigation
- This was auto-generated by Jira Service Desk during workflow import
- In Development
- Pull Request
- When a PR has been opened, should assign to development lead.
- Pull Request Approved
- QA (Editorial)
- QA (Production)
- Ready for Deploy
- Deployed (Production)
- Ready To Stage
- This status is managed internally by Jira Software
- Staged (Acct)
- Staged (Accttwo)
- QA (Acct)
- In Staging
- This status is managed internally by Jira Software
- Next Quarter "Sprint" Backlog
- This status is managed internally by Jira Software
- Ready to Deploy
- This status is managed internally by Jira Software
- Ready for Build
- QA
- Editorial QA
- Selected for Development
- Mitigated
- Not Applicable
- Detected vulnerabilities don't apply to the product version
- Component Not Applicable
- BD_COMPONENT doesn't apply to the product version. It should probably be removed.
- Ready for Launch
- Referred
- Referring this to PM
- Fixed In Later Version
- This issue is fixed in a later release of the same minor version.
- Ready to Release
Resolutions
An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.
- Fixed
- A fix for this issue is checked into the tree and tested.
- Won't Fix
- The problem described is an issue which will never be fixed.
- Duplicate
- The problem is a duplicate of an existing issue.
- Incomplete
- The problem is not completely described.
- Cannot Reproduce
- All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
- Done
- GreenHopper Managed Resolution
- Won't Do
- This issue won't be actioned.
- User Error
- User errors or usage errors
- Not a Bug
- Everything is working as designed.
- Declined
- This issue was not approved.
- Known Error
- The problem has a documented root cause and a workaround.
- Hardware failure
- Software failure
- Resolved