Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-20905

Team-managed projects to share custom fields

XMLWordPrintable

    • 69

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian status as of May 2024

      Hi everyone,

      We are pleased to announce that this feature is now available in Jira Product Discovery as well! Read more about it here.

      Regards

      Carol

      –

      Oct 2023 update

      Hi everyone,

      This feature has been rolled out for Jira Software, Jira Work Management and Jira Service Management. Jira Product Discovery will not be supported at this stage, please feel free to reach out if this is critical to your workflows.

      Regards

      Carol

      –

      Feb 2023 update

      Hi everyone,

      I'm pleased to share that this feature has been rolled out for Jira Software and Jira Work Management (with the exception of customers on Release Tracks). We are working on getting it ready for Jira Service Management over the coming weeks.

      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.

            [JSWCLOUD-20905] Team-managed projects to share custom fields

            Carol Low added a comment -

            8c82428f765f _ thanks for raising this and letting us know - we will look into it.

            Carol Low added a comment - 8c82428f765f _ thanks for raising this and letting us know - we will look into it.

            Jonathan_nor added a comment -

            @Carol Low

            Following the implementation, there is currently no way to easily distinguish company-managed shared custom fields, from system fields.

            Once a company-managed shared custom field has been added to an issue type, hovering over it's name will generate the same message as system fields: "Jira created this field. You can't[...]".

            Shared custom fields should not be treated visually the same as a system fields. The message is inaccurate. Jira did NOT create those shared custom fields, a product admin did. Can Atlassian please fix that?

            Thx

            Jonathan_nor added a comment - @Carol Low Following the implementation, there is currently no way to easily distinguish company-managed shared custom fields, from system fields. Once a company-managed shared custom field has been added to an issue type, hovering over it's name will generate the same message as system fields: "Jira created this field. You can't [...] ". Shared custom fields should not be treated visually the same as a system fields. The message is inaccurate. Jira did NOT create those shared custom fields, a product admin did. Can Atlassian please fix that? Thx

            Pearson Fields added a comment -

            Yes this is critical for my JPD workflow. Please add 

            Pearson Fields added a comment - Yes this is critical for my JPD workflow. Please add 

            Carol Low added a comment -

            0b5d81b92926 - Parent Link field is being replaced by Parent field which is shared – you can read more about this [here|https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758.]

             

            haddonfisher - thank you for the feedback around Jira Product Discovery, it makes sense to me. We have taken note of it and will take it into consideration as we evolve the product!

            Carol Low added a comment - 0b5d81b92926 - Parent Link field is being replaced by Parent field which is shared – you can read more about this [here| https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758 .]   haddonfisher - thank you for the feedback around Jira Product Discovery, it makes sense to me. We have taken note of it and will take it into consideration as we evolve the product!

            Haddon Fisher added a comment -

            684cb16ed833 I can think of a couple use-cases where I would want data that exists in a JPD field to be the same as on JS or JWM issues. One big one off the top of my head would be around things like the "Team" field, where I have lists of teams or teams-of-teams who are involved or interested in a JPD idea; that shouldn't need to be maintained in two places. The other "meta" use-case is around reporting; I can think of a couple of fields I'd want to be able to search for which would include JPD+non-JPD projects.

            The bigger question though is if JPD fields are not instance-wide, can they be shared across JPD projects? This would be a tremendous limitation for people working in scaled Agile environments, because otherwise they would need to centralize ALL of their ideation in a single project to maintain consistency.

            At the end of the day, I guess I would just say "a custom field should be a custom field should be a custom field" - they all should work roughly the same and be usable in roughly the same ways. I recognize this is never going to be entirely true with team-managed projects, but let's not make it any more complicated.

            Haddon Fisher added a comment - 684cb16ed833 I can think of a couple use-cases where I would want data that exists in a JPD field to be the same as on JS or JWM issues. One big one off the top of my head would be around things like the "Team" field, where I have lists of teams or teams-of-teams who are involved or interested in a JPD idea; that shouldn't need to be maintained in two places. The other "meta" use-case is around reporting; I can think of a couple of fields I'd want to be able to search for which would include JPD+non-JPD projects. The bigger question though is if JPD fields are not instance-wide, can they be shared across JPD projects? This would be a  tremendous  limitation for people working in scaled Agile environments, because otherwise they would need to centralize ALL of their ideation in a single project to maintain consistency. At the end of the day, I guess I would just say "a custom field should be a custom field should be a custom field" - they all should work roughly the same and be usable in roughly the same ways. I recognize this is never going to be entirely true with team-managed projects, but let's not make it any more  complicated.

            Tymoteusz Tomaszuk added a comment -

            What about other fields like "Parent Link" ?

            Tymoteusz Tomaszuk added a comment - What about other fields like "Parent Link" ?

            Carol Low added a comment -

            Hey everyone, field sharing is now generally available across Jira Software, Jira Work Management and Jira Service Management projects! Moving this to closed. 

            Carol Low added a comment - Hey everyone, field sharing is now generally available across Jira Software, Jira Work Management and Jira Service Management projects! Moving this to closed. 

            Paul Benati added a comment -

            I use this feature for my Jira Software team-managed projects, which works as expected.  For my use case, I need JSM team-managed projects also to have this feature.  Is there an ETA for JSM?  Thanks.

            Paul Benati added a comment - I use this feature for my Jira Software team-managed projects, which works as expected.  For my use case, I need JSM team-managed projects also to have this feature.  Is there an ETA for JSM?  Thanks.

            Tymoteusz Tomaszuk added a comment -

            Hi, what about Jira Product Discovery product? Are you planning to release this feature as well there? 

            Tymoteusz Tomaszuk added a comment - Hi, what about Jira Product Discovery product? Are you planning to release this feature as well there? 

            Harald added a comment -

            Really? I cannot find it.

            Harald added a comment - Really? I cannot find it.

              684cb16ed833 Carol Low
              19f970a151fc Carl DiClementi
              Votes:
              504 Vote for this issue
              Watchers:
              315 Start watching this issue

                Created:
                Updated:
                Resolved: