-
Suggestion
-
Resolution: Unresolved
-
None
-
60
-
10
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
As a Product Owner
I want to assign stories to a Scrum Team from either Portfolio or JIRA and see it represented in both Portfolio and JIRA
So that I can see the same changes in both tools, depending on who I am talking to and in what context.
The following is currently possible with the Portfolio Team field:
- you can create Shared teams in Portfolio and assign an issue to a team
- It is also possible to Edit an issue in JIRA and change the Team field to one of the shared team.
- It appears in the People section of the Browse Issue view.
- You can add the Team field in the Card Layout on a specific board
Therefore the functionality is almost there but the following is not possible:
- Add the Team field in the Issue Detail View (right pane when you click on an issue in the board)
- Chose the Team field in gadgets in the Dashboards
- Filter board content by Team when using the Agile Board Filter plugin
- Create filters using the Team full names (it substitutes values with IDs) although that's a minor inconvenience.
My main issues are the Issue Detail View and the Dashboard.
- causes
-
JPOSERVER-1780 Not able to bulk edit Team field in JIRA
- Closed
-
JSWSERVER-25237 Adding Team Field to screen triggers history event for every update
- Gathering Impact
-
JSWSERVER-25240 Team field is not properly set after converting a sub-task to an issue
- Gathering Impact
-
JPOSERVER-1823 Make Portfolio Teams visible in JIRA Dashboard Gadgets
- Closed
- is duplicated by
-
JPOSERVER-2379 Make the Jira Portfolio Team custom field available for Jira gadgets
- Closed
-
JSWSERVER-15524 Make the Advanced Roadmaps "Team" field available on the Board Issue Detail View
- Gathering Interest
- is related to
-
JSWSERVER-25334 Scrum board backlog may load all issues and potentially trigger a DB query for each issue
- Closed
-
JRASERVER-68666 Exporting issues to HTML including the Team portfolio field makes resulting file unopenable
- Gathering Impact
-
JPOSERVER-251 Import/Export just for Teams
- Gathering Interest
-
JSWSERVER-25217 Export CSV - Ability to export Team field by name rather than ID
- Gathering Interest
-
JSWSERVER-25255 Add possibilty to make Team field required in field configuration
- Gathering Interest
- relates to
-
JRACLOUD-88879 Portfolio Team field should be a fully supported JIRA field
- Closed
-
JPOSERVER-2621 Allow Team field to be visible even when empty
- Gathering Interest
- links to
- Mentioned in
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC