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

Why, when you program Stages they always go in the next Sprint unless I configure it by hand?

laralg

Hello,

I am testing stages and skills in portfolio. I have created two stages development and QA, I have a release that is off schedule because the QA part goes into the next Sprint. QA

When I plan a Sprint, the development part and QA stay in the same Sprint, but when Portfolio does estimations, they always put QA in the next Sprint. For me this is a lie, if I have enough storypoints left why are you not putting the same things in the same sprint?

I think this is specially wrong if my board was planned that a task was not completed until it went to done (instead of estimation by story points or hours) because that would mean that no task would go completed in a single Sprint.

Do I have to always create the sprints by hand so I get the QA in the right sprint instead in the next one? It seems a by waterfall by me...

In the image, you can see that the Prototipo version will not get done in schedule just because QA cannot go in the same Sprint as development...But in the first Sprint QA and development go together.

Accepted answers

Clare

Hi Lara,

Stages in Portfolio are designed so that each stage is completed in a separate sprint, so you would have to manually assign sprints if you wish to continue using stages.

What might be more useful in your case is using skills instead of stages. Using skills allows you to identify the requirements for an issue without splitting it into multiple iterations.

You can read more about stages and skills in the documentation here if you haven't already. That might clarify some things.

Let me know if you have any more questions

Thanks,

Clare

All comments

Clare

Hi Lara,

Stages in Portfolio are designed so that each stage is completed in a separate sprint, so you would have to manually assign sprints if you wish to continue using stages.

What might be more useful in your case is using skills instead of stages. Using skills allows you to identify the requirements for an issue without splitting it into multiple iterations.

You can read more about stages and skills in the documentation here if you haven't already. That might clarify some things.

Let me know if you have any more questions

Thanks,

Clare

laralg

Hi Clare,

Thanks for your answer, what I do not understand is why it behaves different when I create the sprint that when it calculates on its own. If stages are mean to be one after another then it should behave like that in all sprints, otherwise, I should make all sprints manual in case I want the full task (with all the stages) to happen in the same sprint or everything would have to be left for portfolio to be done magically if I want all the stages in different sprints.

It like, you are forcing me to design all the next sprints manually to have the task completed in the same sprint, it seems very...waterfally?

I will have to use skills for what i want to do, but as I said portfolio forcing the next stage in a different sprint feels really gantt like.

Best regards

Clare

Hi @laralg,

I just had a chat with someone on my team about this and it turns out that there's actually an option in the plan configuration page to stop this behaviour. In the scheduling options section there is an option called 'Stage sprint constraint'. If you turn this off your items will not be scheduled across multiple sprints anymore.

That should be a much better solution to your problem

laralg

Thanks Clare!! Thats exactly what I need ! much better view!!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

advanced-roadmaps