How to show tasks & subTasks on Software / Team Managed Kanban board?

[David Hay]

Hello,

Set up a new project for a Software Space that's Team Managed and using default Kanban board.

We have Epics, Tasks, SubTasks. We need tasks and subTasks to act as the unit of work and both show up on the Kanban board, but we're struggling to figure out how?

How do we achieve this?

[Trudy Claspill]

Hello @David Hay 

As I mentioned in your other post it is not possible to. show Subtasks and their parent items as cards on the board at the same time for a Team Managed project. That is with the board that comes built into the Team Managed project.

It is possible to show subtasks and their parent items as cards on the board at the same time only for Company Managed projects or on boards that show issues based on a filter. You could create a filter to retrieve your Team Managed items, and then create another board based on that filter. For more information refer to these articles:

https://community.atlassian.com/forums/Jira-articles/Multiple-boards-in-Business-and-Team-Managed-Projects-You-bet/ba-p/1719761

https://community.atlassian.com/forums/Jira-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

[Trudy Claspill]

Hello David,

It is not that TM projects are restrictive, per se. Atlassian designed them with different team needs in mind. Customers wanted a project type where the project admins could, among other things, manage their own workflows and create custom fields without impact to other projects and without requiring Jira Admin intervention.

The Company Managed architecture for managing customizations already existed. Team managed was a new customization architecture.

Regarding your questions about moving to Company Managed, the configuration of such projects is managed by Jira Admins and provides the ability to share configurations among the projects. There are other variations in functionality, like Company Managed projects support having multiple types of Subtask issues where Team Managed projects do not. You can find some information on the differences here, but it is not an exhaustive list:

https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/

If you want to move issues that are in your Team Managed project to a Company Managed project there are challenges to that. You can get some information on that topic here:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

If you attempt this I would recommend that you create some test issues in your TM project to test the results of moving them, before moving any critical/production issues.

[David Hay]

Hi Trudy,

Only having one board, not being able to see Tasks & SubTasks on the same board seems pretty restrictive?

Any idea why it would make sense for a Team Managed space to act like that?

I read the link you provided - it doesn't seem to mention preserving Epic -> Task -> SubTask links?

[Trudy Claspill]

I don't have any additional insights on the design decisions Atlassian made while implementing the Team Managed project functionality. I personally am not a fan of it, but it really depends on the needs of the team and the company.

When you move an Epic or a child of an Epic from a TM project to a CM project then the connection between them is broken. This is because Jira does not support having one in a TM project and the other in a CM project. You would need to make note of those relationships and correct it after the move is completed for both issues.

• People have come up with a variety of ways to do that such as creating a new field to note the original Epic key in both the Epic and its child issues. Then after the move automation can be used to look at the child issues, get the pre-recorded original Epic key, find the Epic that also has that pre-recorded original Epic key, and set the child issue Parent to the found Epic.

When you move an issue that is a parent of subtasks, the Move operation will move the subtasks also. Cross project relationships between subtasks and their parent is not supported and a subtask cannot exist without its connection to a parent issue, so the Move operation moves the subtask rather than making it an orphan.

That is why I said the document has only some information about the process, and you should test it out with non-critial issues first. ;-)

You can find a number of posts in the Community on this topic by doing an internet search for jira cloud move issues from team-managed to company-managed

[David Hay]

hi Trudy, thanks, I missed that on the other post.

Unfortunately it seems like I can only use a personal board to get around the restriction.

It seems like Team Managed projects are surprisingly restricted and I should move to company managed? Are there gotchas with those I should be aware of?

What would be the best way to move everything to a new Company Managed project, preserving the current Epic -> Task -> SubTask relationships