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 are Grenhopper Agile i.e. Sprints dislocated from rest of Jira release objects

Axel Gunn

I am using Greenhopper Rabit Wall. Created a sprint with 1 to n stories in it. Stories have 1 to n tasks (btw your story object looks like just another issue with a new type lavel??).

a. Why can I not see Rabit Wall Sprint burndowns via dasboard object?

b. Why do I have to add every task to a release to make it part of my release roadmap? Why can I just not add my Sprint?

c. How come Stories and it's tasks are on the same level i.e. I can add both stories and it's tasks to a relase and the release effort is dulicated i.e. story becomes an effort and it's tasks combined.

Axel

Accepted answers

Renjith Pillai

Rabit Wall? You mean "Rapid Board"?

a. Not possible as far as I know

b. This is not very clear. If you mean that whlie creating stories you need to select the version and later you need to plan them in sprints, that is what scrum all about.

c. Technical Tasks which are sub-tasks of stories are not in same level. How have you created the tasks?

All comments

Renjith Pillai

Rabit Wall? You mean "Rapid Board"?

a. Not possible as far as I know

b. This is not very clear. If you mean that whlie creating stories you need to select the version and later you need to plan them in sprints, that is what scrum all about.

c. Technical Tasks which are sub-tasks of stories are not in same level. How have you created the tasks?

Axel Gunn

Clarifying #B.When I start a sprint. I give it a name. The stories and tasks in the sprint then get worked on.

As far as burndown chart I tried everything in getting that type of chart to appear on by dashboard but the only possibility is burning down releases. My question is then, when I create a sprint, why can that sprint not be a child of a release and i.e. its stories and tasks then automatically by relation) become part also?

Clarifyun #C. It is not normal, even in Scrum, to split a story into tasks and then be able to add both the story and its's tasks to a release. That creates redundance and overlap. I still think that you are trying to patch the system into supporting Scrum.

Stacey Jenkins2

I am also trying to find an answer to a).

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-cloud