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

Ho to capture hierarchical work

Radek_o9e7ty

I am seeking advise / point of view on structuring our project in JIRA.

We have a team, which delivers business projects for various locations under one program umbrella. The structure of the project is pretty standardized and there are approx. 30 steps, which need to be done, in order to complete a project. This relates to things like hotel booking, contract with a facilitator, booking a conference room, content preparation etc. For each story, there is a predefined due date.

Now, it's very convenient to have the individual steps captured in JIRA as Subtasks, project like a story, and overall program like an epic. The problem is, that the story duration varies (from weeks to months) and then subtasks cannot be pushed into a sprint.

Additionally, what is very convenient for us, is that if you clone a story, you also clone all subtasks underneath, so it's easy to add a new project to the program. Subtasks are completed by a single person only.

As we are going to onboard new programs, I would like to have a sustainable way of capturing and managing them.

So wanted to have your opinion on capturing the tasks/project/program/portfolio structure in JIRA.

Accepted answers

Radek_o9e7ty

So for now, we have not restructured our project.

Instead we have kept our stories open for multiple sprints and in Kanban board, we are using a new column "SprintIn". So whatever subtask we want to complete during the sprint, we move from status Draft to status SprintIn during sprint planning. Then the other statuses remain the same (In progress, Withdrawn, Ready, Done ...) and represent the status of the subtask within a particular sprint.

All comments

Uday Kiran Bhaviri_cp1r58

https://wiki.almworks.com/documentation/structure/latest/data-center-and-server/getting-started-with-structure-32223517.html

@Radek

You can try Structure add-on, this add-on will help you to manage all your work in one place with different hierarchy levels.

Hope this will be helpful.

Walter Buggenhout

Hi @Radek,

Take a piece of paper and write down your typical project (plan), in the hierarchy you think it should be. Don't think about issue types yet, just list what you need in the WBS that makes sense to you.

Once you're done, see how many hierarchy levels you have. And think about how you might call them.

Then, consider that Jira - by default and out of the box - offers you a maximum dept of 3 levels: Epic > Task > Sub-task. And be aware that - on a premium plan of Jira Software - you can add additional levels above Epics. See if you can add issue types in Jira to represent the hierarchy on your paper version of the project, add them to Jira and add them to the extended hierarchy. Try to avoid using sub-tasks for the reason(s) you mentioned yourself.

Potentially, set up a project with your default WBS-issues in it and use automation to clone the issues into a new project when you need one.

Hope this helps!

Radek_o9e7ty

Thank you for sharing. Unfortunately, we have company policy that does not allow us to install plugins so I've to use, whatever comes out of a box.

Radek_o9e7ty

Hello Walter, thank you for the reply.

We have done the analysis reg. WBS and so far we need 3 levels. We have a premium plan, so we can use Initiatives and Themes if needed, but then

Can you please elaborate a bit more on the use of automation to clone issues ? Do you mean to clone a story with multiple tasks linked to it ?

Radek_o9e7ty

So for now, we have not restructured our project.

Md saimon_voy0vk

Ho you do you meeting

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud