Hello - I believe JIRA can be used for Project Prioritization Process with the following capabilities. Please confirm whether this is feasible and what specific version of JIRA or Confluence combinations I need to use? For example, Can JIRA Desktop be used for this? or JIRA Project Portfolio, JIRA Agile etc. product suites I need to accomplish this activity? Prioritization Process * Ability to define Project Task with custom properties such as Project#,Description, Created By, Created Date, Proposed by, Business Unit, Description, Sponsor, status, system Impacts etc. * Ability to List Projects and also Group project based on Business Unit * Ability to click Project Number and then see the actual project Description * Create a Dashboard and allow these projects to be prioritized in Kanban Thank you

I still don't know what you mean by Jira desktop, but if pro-fields won't work, I'd still be tempted to go with the project-metadata. Not sure how you can really prioritise projects though. If you've got one team, then it's easy - you just work on one project until it's done, you don't care about the others. If you have multiple teams, the concept of prioritising projects becomes irrelevant to you.

I looked at pro fields last night and it looked promising-until I read reviews. There was another plug-in that would add custom fields at project level. The fields I am looking are basic to any project definition such as Sponsor, Business Area initiating, Sizing Estimate, systems impacted, Release code etc. This is purely for prioritization effort and as you mentioned it is easy endeavor to create a Project of Prioritization as a collection of "Issues", where each issue will have these definitions". that would solve for the problem. But I am not sure how scalable this approach will be. the same can be done with JIRA desktop (I believe) but I am trying to promote something that can be sustained on long term. thank you for all your help on this topic

Very much so. Most people don't seem to need project level fields. For the handful that do, plain JIRA has an addon called "pro fields" which does add some functionality on them, although it might not be what you need, I think it's worth a look before you go into setting up a "project metadata" project. I quite like the "project metadata" idea in some cases. I've done it more than once, but not because I needed project fields, it was more about number crunching I suspect Portfolio isn't quite what you need because it's the newest addition to the Atlassian line and they've been working mostly on fully integrating it (it's an acquistion) with the other big things you can add to JIRA.

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

Project Prioratization

Jeffi Sannapu

Hello - I believe JIRA can be used for Project Prioritization Process with the following capabilities. Please confirm whether this is feasible and what specific version of JIRA or Confluence combinations I need to use? For example, Can JIRA Desktop be used for this? or JIRA Project Portfolio, JIRA Agile etc. product suites I need to accomplish this activity?

Prioritization Process

Ability to define Project Task with custom properties such as Project#,Description, Created By, Created Date, Proposed by, Business Unit, Description, Sponsor, status, system Impacts etc.
Ability to List Projects and also Group project based on Business Unit
Ability to click Project Number and then see the actual project Description
Create a Dashboard and allow these projects to be prioritized in Kanban

Thank you

Accepted answers

All comments

Nic Brough -Adaptavist-

JIRA alone covers the first three, but there's no such thing as "project prioritisation in Kanban" - prioritisation is for issues (a project is a collection of issues with something significant in common - like a product, a team or a process). You can inlcude one, many or all projects in a Kanban board. You'll need JIRA Agile for that.

Portfolio will add a layer of functions and reports that will allow you to do sweeping overviews, planning based on resources and cross-project planning

Versions - use the latest available.

I have no idea what you might mean by "JIRA Desktop" - could be all sorts of things.

Jeffi Sannapu

Nic - Thanks for the update. I meant Projects in a Kanban board. So it seems like if I get JIRA portfolio then I am covered?

Nic Brough -Adaptavist-

You still can't do Kanban with projects - your Kanban boards will only show issues. But yes, I suspect Portfolio will be a good tool to help you with your project planning and prioritisations.

Jeffi Sannapu

Ok. So is there any JIRA suite that allows me to create a dashboard with Projects. So all projects are listed and we are able to see them all at a glance and filter and Group them....and then drill down to get to details? If I model an Issue as Project and define custom fields than I should be able to do this?