| What information is on this page? |
|---|
Standard terminology that is used across most projects in ITS-PRO The types of issue types and fields we currently have in ITS-PRO |
| Who is this page for? |
|---|
| Teams that collaborate in JIRA and categorize different pieces of work |
| Background |
|---|
Teams can collaborate in Jira by breaking down pieces of work into issues. |
ITS-PRO issue types
Issues can represent tasks, software bugs, feature requests or any other type of project work.
| Issue types | Definitions / Use case |
|---|---|
| Milestone | Milestones are the key points in time that sponsors care about, the highest-level accomplishments towards the end goal. |
| Epic | Epics are where we capture Objects that will be delivered as part of a project. These objects normally start with a noun. Some examples can be found here. |
| Task | Tasks are our to-do items and the actions we need to take to deliver an object. These normally start with a verb. Some examples can be found here. |
| Bug | Bug is an issue type for teams to capture software and process defects |
| Story | Free for all. |
| Activity | Activities are time tracking categories for operational work happening outside of projects |
| Project Record | This is an ITSPRO issue |
ITS-PRO system fields
System fields are fields that appear on an issue that are utilized in various places in JIRA (such as built-in reports)
| Issue types | Definitions / Use case |
|---|---|
| Due date | This field is used to track the planned completion of the task / milestone / epic. The PAH uses this date for volatility metrics. If the planned due date gets more refined, it is OK to change the due date. |
| Fix Version / Affected Version / Releases | This field is used to track the scope of work needed for a version to be marked done. In software, bugs are associated to affected versions, and stories and tasks are associated to fix versions. Fix Versions are also used as milestones in the system (Portfolio). |
| Original Estimate | This field is used to determine the effort (in hours) necessary in order to complete a piece of work. We encourage people to change the estimate field as data becomes available. |
| Time Spent / Logged Work | This field keeps track of how many hours a person(s) spends on an issue. |
| Epic Link | This field is used to create a parent-child relationship between an Object and a task. A task can only belong to one Object (via the Epic Link). |
| Issue link | This field is used to link issues or collab pages together. |
| Parent Link (Portfolio only) | This field is used to create a parent-child relationship between an Object and Project Record. An object can only belong to one Project Record (via the Epic Link) |
| Labels | Labels is a global field that is used to tag or categorize any type of work. An issue can have one more labels. This field isn't standardized across projects because anyone can create a label. |
| Components | Components are project-specific fields that can be used to categorize work such as components/modules of an application or workstreams within a project. An issue can have one or more components. Components can only be created by a project admin. |
| Resolution date | This is the actual completed date of the issue (or when it was closed). For project records, when we evaluated the project and agreed that the project is completed. |
ITS-PRO custom fields
Custom fields are fields that the Atlassian team created based on requirements from the PPMO in order to track relevant information.
| Issue types | Definitions / Use case |
|---|---|
| Target start | For project records, this is the actual project start date. For everything else, it is free to use to help you plan (Portfolio as well) |
| Target end | For project records, this is the planned project end date when the project is considered complete. For everything else, it is free to use to help you plan (Portfolio as well) |
| Phase | |
| Work type | |
| Object type | |
| Object complexity | |
| Go Live date (Project Record only) | For project records, this is when the system created by the project becomes available for use. The system is considered live. |
Related Pages
-
ITS PRO Ontology (ITS PPMO)
-
ITS PRO Service Operation Ontology (ITS PPMO)