JIRA Portfolio usability issues/questions

Mira Yu March 5, 2018


I tried using JIRA Portfolio for Backlog grooming/roadmap planning and ran into below issues. Anyone having similar questions/issues ?
We are on JIRA Server v7.3.8.

  • Synching JIRA Plan <> JIRA Software changes:
    • updating JIRA ticket Summary/Story points are reflected instantly in the Plan
    • changing Team assignments/Story points from Plan and committing to JIRA DO not propagate update the individual JIRA ticket.
  • Board Source: I created a new Plan from "High Priority Epics only" board (filtering out low priority Epics) but once Plan is created, any changes made to the Source Board (e.g issues added to/removed from High Priority Epics filter, or update Board filter to include Medium Priority Epics too) is not synched/updated to Portfolio
  • "Later" release:
    • I want to see only a few Release in my plan, not the entire backlog (as we have quite a few Epics).
    • even though I excluded un-wanted releases in the Plan, JIRA puts all un-scheduled issues as "Later" release and it's impossible to exclude/filter out this Later release, which makes Plan Scope view un-usable (overwhelming).



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events