Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

How do you manage releases when code moves to production and fails?

Hi there, if you assign tickets to a planned release and then once they migrate to production, some of the issues fail. Do you assign them to a patch release; therefore mapping the ticket to more than one release? 7.8, 7.8.1 and wait until it passes before closing the prior release?

I am interested to hear about your processes. We do frequent releases of code. High priority tickets migrate regularly.

1 answer

hi @Shalane Sheppard good question :)

I think that a good pattern contains following

  1. testing phase should be contained in the release cycle so you minimize bugs on the production
  2. once the issue is released to the production, you should not reopen it
  3. also the release is released when the artefacts are installed to production -> release is released
  4. if you find a bug on production environment following steps should follow
    1. Bug issue is created
    2. You can use two fields for Bugs
      1. Affected Version -> is set to version(s) for which you found a bug
      2. Release Version -> is empty and is filled in while the bug fix is release to the production

There is maybe another question "How to solve the bug during release cycle" and there might be tons of answers, but some basic answers came to my mind:

  1. If you are using Kanban and you can release often, you just have to prioritize Bug against your Kanban's features
  2. If you are using Scrum and you are releasing once per 2 weeks (or similar short period), you have to evaluate the bug
    1. if it is critical, you should have booked part of your team's velocity for solving these critical bugs and you should fix it ASAP -> release as hotfix version
    2. if it is not critical, you should prioritize it and evaluate if you have enough velocity to solve it in the current sprint OR you should plan it to one of the following sprints
  3. if you are using Waterfall you should be in the production already and
    1. you have probably some Service contract signed with defined SLAs
    2. you should reflect SLAs to the evaluation of the bug and you should fix your bug and release it based on the chosen SLA level

This is really great. So do you make the pass and failed step in the workflow closed statuses so you can release the release? In our workflow, we internally pass and fail and then pass it to the client’s team to pass/fail. So I’m wondering where I would make my statuses complete to be able to consider it closed and then I can create the new bug as you mention. 

We follow scrum, as you mentioned, scheduled releases every 2 weeks. The affected version field is not currently being used but makes perfect sense. 

Hi @Shalane Sheppard it is really based on your processes but what we use is following workflow (simplified "completion part" and for development tasks)

  1. ...
  2. codereview
  3. testing
  4. ready for release
  5. done

So when developer finishes his task, he moves it to codereview and assigns it to other developer. When codereview is done, it goes to testing phase (it can contain creation of test case + testing + separate handling of bug during testing). When the task is tested successfully, it goes to ready for release. You can mark it with following release version and when it is released you can automatically move the issues to done status.

Main information are

  1. you have developed changes or bugfixes
  2. you tested it
  3. you released (+deployed) changes to PROD environment and tasks are Done

 

I'm not sure I provided required answer, so just let me know if you need to consult it further...

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

876 views 14 20
Read article

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