Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

😎 Summary

This page covers the best practice for Jira tickets on the TAPSS board.

🤯 Table of Contents

Table of Contents

Card Definitions

Issue Type

When to use

Template

Useful Example

Story

This is new functionality that needs to be created.

Examples:

  • Creating a new field

  • New page layouts

  • Adding permissions

Persona + Need + Purpose

As a

I want to

So that

Acceptance Criteria:

GIVEN

WHEN

THEN

AND

Bug

Existing functionality is not working as expected.

Examples:

  • User is unable to see fields on a page that they should be able to

  • User is unable to create or reassign records they used to be able to

Feedback/Bug Description: What is not working:

Steps to reproduce:

Expected behaviour (what should the system be doing)?

Business Impact? (e.g. number of users or records affected)

Data used:

Screenshot/Error logs:

Link to the record:

Teams impacted?

Epic

This is an large overarching body of work that will be broken down into different tickets.

Examples:

  • TAP strategic priorities

  • Projects to overhaul existing functionality or create new functionality

Summary:

In Scope:

Out of scope:

Any known dependencies:

Teams impacted:

Project team:

Improvement

This is to update or change existing functionality.

Examples:

  • Updating picklist values

  • Updating permissions to include or exclude data

  • Updating existing page layouts

Persona + Need + Purpose

As a

I want to

So that

Acceptance Criteria:

GIVEN

WHEN

THEN

AND

Task

This is for non-development related activity.

Examples:

  • User provisioning requests

  • Test case completion

Issue:

Why are we doing this?

Impact? (e.g. number of users or records affected)

Teams impacted?

Xray Test

For use of the Testing team.

N/A

N/A

Test Set

For use of the Testing team.

N/A

N/A

Test Plan

For use of the Testing team.

N/A

N/A

Test Execution

For use of the Testing team.

N/A

N/A

Risk

Not in use. Do not use.

N/A

N/A

Issue

Not in use. Do not use.

N/A

N/A

Precondition

Not in use. Do not use.

N/A

N/A

T-Shirt Sizes

XS =

T-Shirt Sizes

How long will it take?

XS

2 hours

S

=

1 day

M

=

3 days

L

=

5 days

XL

=

10 days

Jira Fields

BA working on tag - this card is being reviewed and finalised by the BA in conjunction with the stakeholders, to get to DoR for backlog refinement

Flagged - where the card is not blocked but there something needs to be resolved within the sprint. Once flagged, enter a free text explanation of the issue for resolution.

Card Priorities

Bugs priority types - “Critical”, “Major”, “Minor' and “Trivial”

Stories and tasks priority types (MoSCoW) - “Must have”, “Should have”, “Could have” and “Won’t have”