-
Suggestion
-
Resolution: Fixed
-
513
-
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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.
Workaround
As a workaround, you might use the Advanced field editing - JSON option to define the value of the Team field. The Edit Issue fields action will then look like below:
{
"fields": {
"Team: {
"id":"1",
"title":"Plan-specific team",
"isShared":"false"}
}
}
For the trigger, the event "Issue updated" and using the "Advanced compared condition", the value below can be used to test if the "Team" field was updated:
{{#changelog.Team}}{{from}}{{/}}
PS: this is just an example, you must see how the fields are set in your Jira cloud site and adjust it accordingly.
- is related to
-
JRACLOUD-88289 Advanced Roadmaps fields (Team, Parent Link) don't show up in Automation For Jira
-
- Closed
-
-
- Gathering Interest
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Gathering Interest
- Mentioned in
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-88879] Portfolio Team field should be a fully supported JIRA field
Team should be a fundamental field & support basic search/sort operations for all kinds of reporting within Jira & Confluence reports (using Jira macros) at minimum.
This is a critical requirement, using any workaround is hacky and shouldn't be thought as a "solution" to the problem.
+1 to all the comments. The Team field being fully supported in Automation/Gadgets/Structure is critical to fully leveraging Roadmaps across JIRA. My team (130) just adopted Roadmaps and now we are frustrated due to this partial roll out.
Has anyone got the workaround to actually work? Tried many different calls and Team will not assign, keep getting "is not valid" response. This feature is crucial for the use of Teams.
+1. You forced us to use Team field (since this is the only way to use Advanced Roadmaps) but it's lacking support in Automation. Thanks!
How can we get the timeline for the fix? We need the "Team" field for reporting, it is very crucial for us.
What does it take to get this ticket addressed? This is a very painful issue for my company and is impacting 40+ teams.
The workaround is very messy and unnecessary. Why do we have to jump through the hoops for such a simple fix? Please get it done.
+1 we can "solve this problem" using the JSON to update the issue, but it's "one more workaround" necessary in JIRA.
Hi everyone,
Thank you all for sharing your feedback and desire for the Team concept in Jira Plans to be made a native supported Jira field.
I'm closing this ticket following the rollout of our public roadmap item: Unification of team concepts
Since December 2023 we have been rolling out a unification of our Shared Teams with Atlassian Teams. Shared Teams (now deprecated) have since been migrated to Atlassian Teams. You can access and manage these teams from the ‘Team’ dropdown in the header across Atlassian Cloud products that support it.
Atlassian Teams are now what is used in Jira plans, with the same capabilities that our Shared Teams previously provided.
Along with this unification are some additional benefits that come with this change such as an insightful Team profile page, @mentions for teams and more.
If you’re interested to learn more, you can check out these resources:
Kind regards,
Rhys | Product Management, Advanced Planning