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

How to make task/subtask in different projects?

Shivam

I have a system architecture where I have a backend api server, 4 apps. Accordingly, I have 5 different boards. Now, if I create a task/story in my server project, I want the ability to create 4 diff sub tasks across 4 diff boards as these all are dependent on backend server. As of now, I can only create sub task in the same project and then move it to different board, which is not a good way. Can it be achieved through current JIRA architecture or is there any other way I could achieve this functionality with minimum changes required?

Accepted answers

All comments

Nic Brough -Adaptavist-

There are a couple of fallacies here:

Boards are not issue containers, they are views that select things you choose to see. "Move issue to board" is nonsense, as they're not containers.
A sub-task is part of an issue. An issue is contained in a project. It does not make sense to say that a sub-task is in a different project to its parent issue.

But, yes, you can do what you describe. You need to define your board filters so that they select the issues you want to see on each of them. Your situation needs some slightly more complex filters than most of us need, but it can be done.

Tom Leser

I disagree. I've seen similar posts where people say you can't do this but you accomplish the same thing by linking to another issue type in a separate project.

The benefit on the ability to move a subtask to a separate project is the usability and ease of creating the ticket and having the automatic link to the parent.

Nic Brough -Adaptavist-

I'm not sure what you disagree with. A sub-task is part of an issue, and an issue lives in a project? That's how it is, so there's nothing to "disagree" with there. It's total nonsense to have a sub-task in a different project, they're part of the issue.

Andre Schaub

@Nic : You seem to suffer from operational blindness.

An issue is defined a a problem or topic that needs attention or a solution.

It's absolutely common to seperate different development branches in different projects. E.g. you develop your Frontend in php and your backend in Java. Both can have absolutely differend needs, workflows, members and other needs. So you split these into different projects.

If you are working on a specific problem, e.g. developing a new workflow for a new product, the main project may be the frontend because 95% of the workflow happens there. So you place the issue in the project frontend.

But: you may need some endpoints for transferring data to your systems via the backend. These are tasks that have to be placed in the project backend.

For a halfway reasonable workflow you should be able to create tasks in different projects and link them.

Easy to understand as 1, 2, 3.

Welcome!

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

Quick Links

Find more posts tagged with

jira