Raking issues in Plan individually within each Team for Program Management

[Alan Sanders]

Hi 

I need to be able to set up Jira for my Org and the teams in such way that each Team will be able to rank Projects individually on their Plan.

Say I have a Jira project.

In this project , there are 100 Projects (Issue Type=Project). Those are the projects multiple teams in our org are working on.

Each Team has their own prioritization for every one of those projects. A single project can be ranked (prioritized)  as "1" for one team, while another team has very little lower priority involvement and needs to rank this project as "10" in their Plan.

Is this possible to achieve in Jira cloud and if yes - how?

I've been playing around and it seems that the ranking within an individual Plan is reflected on all Plans for all Teams.

Thanks!

[Vit Mee]

Hey @Alan Sanders 👋

It sounds like you need a flexible prioritization system within Jira that allows different teams to rank and manage their projects independently based on their unique priorities. While Jira Cloud offers robust project management capabilities, it might not natively support distinct, team-specific prioritization views within the same project.

However, you can achieve this by integrating Ducalis.io with your Jira setup. Ducalis.io is an advanced prioritization tool that allows you to sync your Jira backlogs into individual boards. Here's how Ducalis.io can cater to your specific needs:

1. Individual Team Boards: You can create separate boards for each team in Ducalis.io. Each board can be connected to your Jira project, allowing teams to import their specific issues (projects in your case).
2. Custom Prioritization Frameworks: Every board in Ducalis.io can have its prioritization framework. This means that each team can assess and rank their projects based on criteria that make the most sense for their objectives and workflow.
3. Aggregated Board for Holistic View: Ducalis.io offers an aggregated board feature besides individual boards. This board can provide an end-to-end view of priorities across multiple projects, helping to align different teams and understand the overall priority landscape.
4. Automatic Sync with Jira: After the teams have prioritized their projects in Ducalis.io, the prioritization data can be synced back to Jira. This synchronization can be done individually for each board or collectively through an aggregated board, ensuring that Jira always reflects the most up-to-date priorities set by each team.

We use Ducalis.io precisely in this way:

We have multiple boards with a team, backlog, and prioritization framework. This approach has given us the flexibility to cater to each team's unique needs while maintaining a cohesive understanding of organizational priorities through the aggregated board.

For more information on how to set this up and to get started with Ducalis.io, you might want to visit the following resources:

• Ducalis.io Integration with Jira Cloud
• Ducalis.io Integration with Jira Server
• Ducalis.io on the Atlassian Marketplace

I hope this helps! If you have any more questions or need further clarification, feel free to ask.

Best regards,

Vit from Ducalis.io

[Trudy Claspill]

Hello @Alan Sanders 

Welcome to the Atlassian community.

Jira has a built in Rank option which is the one you are using when you drag and drop issues to reorder them in an agile board, a backlog, or a timeline. Ranking in this case is global - an issue's rank is relative to all the other issues in Jira, and anywhere data is sorted by Rank this will be reflected.

So, you cannot use the drag and drop ranking method to let teams rank the same issues in different orders.

In what context do the teams need to visualize their individualized prioritization for these projects? Would that be in an agile board, in a backlog, in a Timeline, ...? And does that need to include showing the child issues under those "Project" issues?

The teams will need another way to indicate the priority of the projects within their team, without affecting the priority indicators set by other teams.

Off the top of my head the only thing I can think of is to have a unique priority field for each team to set: TeamA-Priority, TeamB-Priority, TeamC-Priority.

However, if the teams' agile board filters are changed to use that custom priority field to order the issues, then the team will loose the ability to otherwise drag and drop issues to affect global Rank.

[Alan Sanders]

Hey Trudy. Thanks a lot for an elaborate answer.

The ": TeamA-Priority, TeamB-Priority, TeamC-Priority" fields is my plan B.

The context here is daily reporting by each team's Lead to the Org. Director on the status of each project - one  board per Team.

The individual ranking (or sorting) will provide clarity to the Director on prioritization of projects for each team. 

The view needs to show one level down below each project for the underlying "epics"/high level tasks. 

Thanks again!

[Trudy Claspill]

What is the presentation style you need for "daily reporting by each team's Lead to the Org. Director on the status of each project"? Is the Org. Director going to be viewing an agile board? 

You might be able to create a special filter just for this presentation where all the issues you want (for a team) are selected, and then for the ORDER BY clause you use

ORDER BY "TeamA-Priority" desc, RANK desc

You would need to be copying the Team Priority value from the parent issue to the child issue. And each value for Team Priority would need to be unique so that you didn't have two "projects" and child issues mixed together.