nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Release ticket process in the organization.

Madhi Ramamoorthy

Effective fields to capture the release ticket .

Fix Version

Deployment date and time.

QA Details of types of testing.

Approvals based on the organization standard.

Release summary

Ticket ready for review.

Do you feel any other things need to be added?

Comments

David Woo_ik8ksn

I would probably cross-reference if the work done was related to a BUG/Defect, or enhancement.

Varsha Joshi

Hi @Madhi Ramamoorthy

Welcome to the community!

For us one of things that is critical to know which release version the jira was included in.

Susan Waldrip

Hi @Madhi Ramamoorthy , Welcome to the Community!

You might want to know who the testers were, for traceability, and include a link to test results (if possible) for future reference or audit considerations.

David Woo_ik8ksn

Agree if within the organization. If planning to hand off to clients or publish online, then no, no one needs to have names of testers.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

release

release-management

rag