Any connection between Portfolio Drag/Drop Prioritization and JIRA Priorities?

[Alex Lee]

Hello,

I have a question about the JIRA Portfolio Priority System as discussed here:

https://confluence.atlassian.com/jiraportfolioserver/re-prioritizing-work-items-802170527.html

(This allows users to drag and drop to reorganize and re-prioritize work in the Plan view. You can hit "Calculate" and it'll rerun the algorithms for the scheduling portion)

Additionally, in just regular ol' JIRA, it has it's customizeable priorities. (Default for Software: BLOCKER > Critical > Major > Minor > Trivial)

My current understanding is that these two sets of priorities are totally separate. That a change to one will have no impact on the other. Changes to Portfolio priorities doesn't effect JIRA priorities, and vice versa.

Is this correct?

Thanks!

EDIT: Looks like Portfolio uses a field called "Rank" for it's assessment. So as a secondary, is it intended for regular JIRA to touch or work with this Rank field at all?

[Petar Petrov (Appfire)]

The Rank field is used by JIRA Agile (JIRA Software now) for ranking user stories within a board. When you change the order of issues within a board - this is the field that gets updated and stores that information.