Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best Practice for Workflows that track deployments across environments

Our Infrastructure Operations team is currently moving from a standard Kanban type workflow to something more customized to our actual process.

Specifically, we will receive a request to deploy a change to Production. We will first deploy this change to our lower environments and have the developer verify the change in each environment before it is deployed to Production.

Our pain point currently comes from deploying to a lower environment, waiting for the dev to validate which can often take days/weeks. In the meantime we have this story sitting on our Kanban board which requires we give our PO status updates even though it is not currently actionable by our team.

My current thought exercise as to what I think could work is as follows (we will be utilizing a Jira automation tool):

1. Create a specific issue type for deployments. This will have a workflow that has statuses for "Deploying to Environment X" as well as "Awaiting Dev Review"

2. When a new issue is created with that type, have it auto-generate sub-tasks for deployment to each environment.

3. When a sub task is closed move the issue to "Awaiting Dev Review" and assign issue to the dev who submitted the request.

4. Rinse and repeat until we make it to Production.

Any feedback would be appreciated. Im not sure if Im overthinking here, or missing something simple that could help to improve this process without re-inventing the wheel.

 

Thanks in advance!

0 comments

Comment

Log in or Sign up to comment
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you