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; } } }

Roadmap warning signs on tickets/issues

unknown

Hello ! Im Product Owner and with my team we are using the Release/Version feature in Jira.

Recently I'm seeing that all the tickets done and linked to a release have a warning sign next to them saying that the ticket should be done after the release in which they are linked.

I don't understand what it means. (I use the french version and maybe the translation is wrong).

Our flow is quite simple, we have the TODO->DOING->Code Review->Testing (where I can test the ticket on QA)->Validated (when I'm ok with the feature/fix)->Done

When a ticket is in a Validated state I affect a Version to it. And then deploy it to production.

image (28).png

The weird thing is that I can see this message and warning sign on each tickets linked to a version and to me it makes just no sense.

Accepted answers

All comments

Walter Buggenhout

Hi @[deleted]and welcome to the Community!

My best guess is that you assigned start and end dates to your issues (either on the issues individually or by adding them to a sprint) and that the version you added them to has different, conflicting start and end dates.

You can check that by comparing the start/end dates of you individual issues to the start/end date you can find when you navigate to the releases in your project.

Hope this helps uncover the mystery!

unknown

Hello @Walter Buggenhout ! Thank you for your welcomeness.

I fixed the warning sign following your instructions, thanks.

Nonetheless, I feel that the release / version should not work that way. With continuous deployment processes and all, I need to create multiple versions deployed within a Sprint.

It makes no sense to match the delivery date of a version with the end date of a Sprint. In my case I have to set the delivery date to a future one to not have the warning sign.

The mystery is solve anyway, thanks,

David

Walter Buggenhout

Hi @[deleted],

I totally agree with you on the continuous deployment statement. Apart from tooling, in that same, continuous deployment scenario it does not make much sense to include all your (technical) releases on a roadmap either. A roadmap is meant primarily to visualise the key milestones (such as MVP releases or PI's in SAFe) for new product development. For those releases they do make sense.

You can avoid those warnings by not setting end dates to your technical releases. Until of course, you release them 😅

unknown

Yeah sure

Cyprien Autexier

Hi @[deleted]

Effectivement il y a une erreur dans la traduction. L'avertissement devrait être quelque chose comme.

Ce ticket devrait se terminer avant la livraison à laquelle il est assigné.

En pratique l'avertissement apparaît parce que la date d'échéance du ticket est postérieur à la date de fin de la release/version.

J'ai ouvert un ticket avec l'équipe de traduction et ça devrait être corrigé prochainement.

J'espère que ça clarifie les choses, n'hésitez pas à nous recontacter si ce n'est pas le cas.

Merci encore pour le signalement,
Cyprien

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

version

release

roadmap