Details
-
Suggestion
-
Status: In Progress (View Workflow)
-
Resolution: Unresolved
-
None
-
101
-
Description
Hello all,
Thank you for continuing to share valuable use-cases and feedback on this ticket. To provide some detail: we are enabling Team-managed projects to be able to re-use global custom fields, while maintaining how custom fields created in Team-managed projects work today.
We've made steady progress since the previous update and still tracking to the same estimate of Sep-Nov 2022.
We are now preparing for an Early Access Program for this feature - estimated to take place in August. If you are interested, please reach out to me at clow@atlassian.com
I'll continue to provide periodical updates here over the coming months.
Thank you,
Carol Low
Product Manager
Summary
Team-managed projects are the perfect tool for getting non-technical teams into Jira and are finding early success with this.
Meanwhile, it is important that a balance is struck between organization-wide structure and the "do it yourself" mentality of next-gen projects. We have configured important custom fields on our "classic" projects that help us keep in sync and report cross-team.
As such, please allow custom fields to be shared across team-managed projects and company-managed projects.
Attachments
Issue Links
- relates to
-
JRACLOUD-78777 Sort feature not working properly with team-managed filters in gadgets
-
- Closed
-
-
JSWCLOUD-20760 REST API endpoint (Get user default columns) returns incorrect columns with duplicate custom fields
-
- Closed
-
-
JRACLOUD-78778 Order by statement not working properly with team-managed filters
-
- Gathering Impact
-
-
JSWCLOUD-18756 Restrict Team-Managed (Next-Gen) custom fields name if already exists another custom field with the same name
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...