Skip to end of banner
Go to start of banner

Creating the 'Fix Version' and the Release in Jira

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Instructions

  1. Decide what Jira ‘Project’ to use for creating the Fix Version and all subsequent task tickets for the project.

    1. If the project will primarily be completed by one division or workgroup(s) within a division (CTO, Infrastructure, Projects & Innovation, Technical Support), then the release and fix version can be created within the division’s project.

    2. If project will involve substantial amounts of work across divisions, the release and fix version should be created in the Projects & Innovation project container. The release and fix version should be created by the Director for the Projects & Innovation division.

    3. Enterprise level projects that will involve multiple departments may warrant the creation of a new project container within Jira. This would be determined in consultation with the Director for Projects & Innovation.

    4. Releases and fix versions should not be created or managed through the Technology Service Desk container.

  2. Once you have decided on the project, create the release in the Releases section of the project.

    1. Naming your project:

      1. Format: Product: Release name - Version: x

        If you do not have a release name or version number, then you can use the following conventions:

        • If you are upgrading the product. use: Upgrade

        • If it is the first time installing or using the product, use: First install

        • If you are adding functionality or fixing issues to the product and you do not have a release naming convention, then you can use the year. For example: 2020

        • If you do not have a version number, then you can either start one or use the year. For example: 2020.0

        For example: Jira: Upgrade - Version: 7.4.x

  3. Create the Fix Version ticket within the Jira project using the guidance that follows:

Fix Version

Field Name

Description

Required

Project

Select the project space where the fix version ticket will be located

(tick)

Type

Select ‘Fix Version’ as the issue type

(tick)

Summary

Use the name of the release

(tick)

Description

Describe what is going to be accomplished or what problem you are solving

(tick)

Components

Select the division or workgroup that will be primarily responsible for completing the project.

(tick)

Priority

Use the table below to determine the appropriate priority level for the project.

Fix Version

Select the Fix Version from the drop down menu. (This pulls from the release section completed in Step 2 above.)

(tick)

RGT framework

  • Run - Operate and maintain

  • Grow - Enhance and expand

  • Transform - Innovate and drive

(tick)

Project change

  • Planned - Work that needs to be completed, but was scheduled ahead of time.

  • Unplanned - Work that needs to be completed, but was NOT scheduled ahead of time.

(tick)

Resource categorization

Select the appropriate resource

(tick)

Technology focus area

  • Student

  • Teacher

  • Instructional Administrator

  • Technology Services

  • Operational Staff

  • District business/compliance need

(tick)

Initiator

  • Community

  • District

  • Technology Services

(tick)

Assignee

Assign to the designated Project Manager

(tick)

Initiative

The initiative that the project aligns to is selected after the ticket has been created. Once the ticket is created, select Initiative from Connected Items listed in the Details box that appears in the right column of the ticket.

Not at create

Priority

Priority Level

Description

Highest

  • Mandate - Executive Leadership/Board, legal/compliance

  • Impacts functioning of core/foundational service if not completed

  • Other services/products depend on it project being completed

  • Work stoppage will occur and no workaround exists (Product is nearing or past End of Life, Reliant on outdated technology)

  • Essential/critical to customer

High

  • Aligns with CSIP Plan/district initiatives OR

  • Aligns with department program evaluation OR

  • Aligns with department goals/objectives

  • Direct impact on students/student achievement

  • Integrates multiple processes

  • Streamlines work processes

  • High impact to customer

Medium

  • Aligns with CSIP Plan/district initiatives OR

  • Aligns with department program evaluation OR

  • Aligns with department goals/objectives

  • Direct impact on students/student achievement, impact 

  • Integrates multiple processes

  • Streamlines work processes

  • Impact to customer

  • Impact on business is to a lesser degree when compared to a high priority project

  • Important but not urgent

Low

  • Unknowns about project

  • Uncertain about user impact or impact for low number of users

  • Potential negative risk outweighs benefit.

  • Non-essential

  • Nice to have

  • Consider abandoning project

Filter by label

There are no items with the selected labels at this time.

Page Content

  • No labels