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

Add existing custom fields to team-managed projects e.g. Tempo fields

XMLWordPrintable

    • 3

    • 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.

      As a user working with a Next-gen project I would like the ability to add existing custom fields to the a project. 

       

      My company uses Tempo for our time tracking and we have invested some time in integrating tempo accounts with our CRM to keep an up to date list of possible client's to track time against. We would like to use the new next-gen projects but we are unable to add existing custom fields so although the tempo plug in works to log work we can't associate that work with a specific client.

       

      This would also be useful for other fields which are common to many of our development teams. For instance we have dropdowns for other business units that need to review our work that should be consistent across projects. Maintaining these separately in the current next-gen projects is onerous.

            [JSWCLOUD-17484] Add existing custom fields to team-managed projects e.g. Tempo fields

            Anusha Rutnam added a comment -

            I'm still looking into the Tempo use case but 0b7289ba80bd I think what you've described is now possible since the change announced here: https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Announcing-the-ability-to-re-use-global-custom-fields-in-team/ba-p/2209113

            Docs: https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/#Customizeanissue'sfieldsinnextgenprojects-Reusecustomfields

            Anusha Rutnam added a comment - I'm still looking into the Tempo use case but 0b7289ba80bd I think what you've described is now possible since the change announced here: https://community.atlassian.com/t5/Jira-Cloud-Admins-articles/Announcing-the-ability-to-re-use-global-custom-fields-in-team/ba-p/2209113 Docs: https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/#Customizeanissue'sfieldsinnextgenprojects-Reusecustomfields

            David Quiram added a comment -

            Our use case is having fields that are standardized for the company. In the case of our internal helpdesks, a "departments" field is something that applies company wide and we just have one point for updating. If we had to re-create that field in our projects, we would have to make sure every project is checked and that the field is updated to reflect department changes. 

            David Quiram added a comment - Our use case is having fields that are standardized for the company. In the case of our internal helpdesks, a "departments" field is something that applies company wide and we just have one point for updating. If we had to re-create that field in our projects, we would have to make sure every project is checked and that the field is updated to reflect department changes. 

            Jaap Buitelaar added a comment -

            We created some dashboards using custom fields to get info on all projects.

            For this, we use some custom fields. So this is why we need global custom fields (like single select list box) for next-gen projects.

            Jaap Buitelaar added a comment - We created some dashboards using custom fields to get info on all projects. For this, we use some custom fields. So this is why we need global custom fields (like single select list box) for next-gen projects.

              Unassigned Unassigned
              58ce7cc5-1028-44bc-8797-dc9b11641581 Deleted Account (Inactive)
              Votes:
              21 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: