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

What is the best way to manage two types of content?

Stephen C Hauer

Hello,

Im new to Jira and trying to better understand how I should be managing a team that has two unique workflows. We are using sprints to manage our workload going forward because it works best with our current structure. What Im trying to figure out is the following

I have two unique workflows I need to support and don't really know how to set this up in Jira.

Production: Backlog>ToDO>In Progress>IN Verification>Done
Generate Backlog: Ideas>Analysis>Scoping>Ordering>Photographing>Send to Backlog
(Send to Backlog refers to the first workflow)

The thoughts that are going through my head are as follows.

Should this be done using new projects?
Should this be done making a new task type?
What is the more scalable solution?

Any feedback people have on this topic would be greatly apricated.

-Stephen

Comments

Janusch Rentenatus

You can create two projects, each can have its own type, each can have different state transitions.

If you need it, you can define your own additional states differently in each project.

Aron Gombas _Midori_

To me this sounds that it could be best modelled with 2 different issue types. (If there are other differences, not only the statuses, but for example fields, between the two "kinds", then that also encourages using two issue types.)

Then you can associate a different workflow with each issue type.

(You can use the two issue types within the same, or in 2 separate projects, that freedom is not lost with this approach.)

Stephen C Hauer

Thanks for the feedback. I think your right @Aron Gombas _Midori_ @Janusch Rentenatus Both options seem solid. I will try to have the issues types determine the workflow for now. Then IF I hit a issue I know I can make a project that will provide more control.

Thanks for the brainstorming session guys!

Stephen C Hauer

I found having one project and with multiple boards works the best for me. I dont have to deal with task handoffs and reassociating data.

Janusch Rentenatus

Thanks for the feedback. Many greetings.

Jimi Wikman_ex43zi

I agree with this.

You basically have two completely different processes where the first is a build process and the second is the strategic and financial process.

They should never be in one JIRA project because they do not have a 1-1 relation and you will have tasks that are strategic in size.

Two projects and two workflows: One where you plan and scope and one where you work.

Nic Brough -Adaptavist-

I wouldn't do that. It sounds like it should be one project, but two workflows (which means two different issue types in that project)

If you have them in the same project, you can share things like components and versions, but still handle them with separate boards if you want to.

Jimi Wikman_ex43zi

Two workflows still means that you need two boards or a shared set of statuses. There is no benefit in the visualization of work, and it just becomes confusing to have two completely different processes in one project.

Having the same components can be done anyway, but having in one project will mix operational and strategic components that will mean that neither team have a focused setup for their work.

You would not have a release for a strategic workflow. That will only feed operational tasks, which is the only place you would have releases.

An easy way to determine if you should have one project or two is to put everyone that works in both flows, including stakeholders, in the same room and see if everyone in that room need to know everything that is on the board.

If they do, then keep it in one project.

If they don't then use two projects.

The worst thing you can do is to force people to filter of change views to see what they need to see to focus on their work.

Clutter is never an optimal solution. Focus is.

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