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
-
Bug
- A problem which impairs or prevents the functions of the product.
-
New Feature
- A new feature of the product, which has yet to be developed.
-
Story
- A user story. Created by JIRA Software - do not edit or delete.
-
Task
- A task that needs to be done.
-
Improvement
- An improvement or enhancement to an existing feature or task.
-
Encroachment - Tier 2
-
Billing
-
Permit
- Permit Issue Type
-
Process Improvement
-
Report Inquiry
-
Re-Run Existing Report
-
Training/Skill Enhancement
-
Research
-
Annual Budget
-
Program/Business Analysis
-
Policy
-
Special Project
-
On-Boarding
-
Demonstration
-
Cost/Revenue Analysis
-
Hallway Planning/Brainstorming
-
Report Correction
-
Meeting Attendance
-
Report Improvement
-
Miscellaneous
-
New Report
-
New User
- New JIRA User/Requestor and Permissions
-
PTO/Holiday/Flex
- Used for Time Tracking PTO Usage, will be excluded from production reports.
-
Intake
-
Document
- A document requiring approval.
-
Office
-
CIP
-
Utility
-
Parking Accessibility Review
-
Accessibility Citation
-
Small Cell
-
Vacation
-
Encroachment
-
Relinquishment
-
Accela Development
-
Tier I
-
Report
-
PO Other
- Other can be items like access or excel files, powerapps, flows, and other documents
-
Project
-
Internal
-
SAi
-
Citation Audit
-
Shift Audit
-
Collection
-
Administrivia
-
Other 'One Off' Review
-
Administration
-
GIS Request
-
General
-
Jira
-
Street Rename
-
Service Request
-
Paid Leave
-
Closed
-
Regulatory & Policy
-
Floodplain Management
-
GIS/Mapping
-
Data Analytics
-
Continuous Improvement
-
Other
-
Field
-
Plan/Program
-
Internal Procedure
-
User Violation
-
Operator Violation
-
Business Plan
-
Metrics Development
-
CI Engagement
-
Storymap
-
2 Hour Remedy Period
-
Moving Violation
-
Ad-Hoc Report
-
Standalone Task
-
System
-
Wellness
-
Reporting/Data
-
Other Agency Assistance
-
Private Development
-
CIP 70
-
Dispatch Card
-
Personnel Related
-
Administrative
-
Flood Study
-
Data Inquiry
-
Revocation - Encroachment
-
Encroachment - Tier 1
-
Encroachment - Tier 3
-
Case
-
Boot Card
-
Valet Card
-
Database
-
Epic
- A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
-
Venue
-
Valet Operator
For Sub-Task Issues
-
Individual Task
-
Technical task
-
Coordination
-
Transportation
-
Wastewater
-
Erosion Control
-
Floodplain
-
30 Day Followup
-
Strategic
-
60 Day followup
-
Sub-task
-
90 Day Followup
-
Coaching Activity
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.
-
Critical
- Critical Request
-
High
- High priority request
-
Medium
- Normal priority request
-
Low
- Low priority request
-
Normal
- Normal
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.
- Parking Lot
- Defined - Ready for Work
- Parking Lot - Not Ready For Active Path
- Initial Core Work Completed
- External Testing As Required
- Testing Complete
- Deliverable Docs/Archive Gathered
- Done Pending Other Dependency
- Core Work Completed - No Testing Needed
- ATCMTD Required Testing Engagement
- ATCMTD Internal Testing Completed
- Mgmt & Team Agreement to Include in Active
- Tasks Defined and Agreed
- 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.
- Building
- Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
- Build Broken
- The source code committed for this issue has possibly broken the build.
- Pending
- Pending outside item
- Ongoing
- Any issue that is ongoing with no foreseeable end.
- To Do
- Done
- Under Review
- Approved
- Cancelled
- Rejected
- Waiting on Customer
- Waiting on customer information
- Waiting for Next Submittal
- Waiting for next submittal
- Dispatched
- Unit assigned and dispatched
- PreOpen
- Draft
- Second Review
- In Review
- First Submittal
- Second Submittal
- Public Notification
- Council Action
- Backlog
- Selected for Development
- Denied
- Upcoming
- Audit Pending
- Succesful
- Coachable
- Won't Do
- Coached
- In Progress
- This issue is being actively worked on at the moment by the assignee.
- To Do
- Done
- Assigned
- Blocked
- Time Marked
- Sent for Pick Up
- To Do
- In Progress
- Done
- BLOCKED
- Offense
- In Use
- Being Built
- Connection Pending
- New Entry
- Decommissioned
- Disputed
- Permanent
- Login Pending
- Awaiting Application Info
- Logged In (Review Period)
- Fees Due CR Not Sent
- CR Sent Denied Status
- Conditionally Approved
- ORD/RES/Permit Drafting
- Supervisor Review
- Pending Approval
- Done Approved
- Done Withdrawn
- Done Denied
- Active
- On Hold
- Sent to Enforcement
- Additional Info Needed
- Invalid Request
- Party Advised
- dwa
- Duplicate
- Keep
- Warning Issued
- First tier violation provided
- Second tier violation provided
- Customer Resolved
- City Resolved
- Third tier violation provided
- Booted
- GOA
- Impounded
- Tow Eligible
- Booter Dispatched
- Released
- Admin Release
- Release Eligible
- Escaped
- Pending Assignment
- Inactive
- Follow Up
- Valid
- To Do
- Defined Work In Progress
- Done ("Deployable")
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.
- Complete
- Ticket or task is complete.
- 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
- Ticket or task is complete for now, expected to be re-opened.
- Won't Do
- This issue won't be actioned.
- Done
- Work has been completed on this issue.
- 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.
- Warning Issued