• 13
    • 36
    • Hide
      Atlassian Update –

      28 February 2018
      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      There are several third party add-ons that solve many of the use cases mentioned here:

      We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, and especially since third party add-ons are available, we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 28 February 2018 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  There are several third party add-ons that solve many of the use cases mentioned here: Profields JIRA Metadata Plugin JIRA Project Specific Select Field . We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, and especially since third party add-ons are available, we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      As JIRA Administrator I need the ability to create custom fields for project in pretty much the same way as for issues. This way I will be able to store additional information per project and search for projects and issues based on these additional criteria.

            [JRASERVER-1991] Custom fields for Projects

            Hi Everyone!

            Profields has evolved to focus on a unique purpose, to be the leading project tracking solution in Jira, now named Projectrak.

            Why have we made the change?
            This decision is not just a name change to give the former Profields a more appropriate name according to what it can do. Profields was born as an app to provide fields to Jira projects. Today Projectrak is much more than that; it has gadgets, different views, integrations with third-party marketplace apps, and more features that enable you to keep track of projects as you have never been able to do with Jira.

            We are working on a new Cloud version. Stay tuned!

            Cheers,

            Leo

            Leo Diaz | DEISER added a comment - Hi Everyone! Profields has evolved to focus on a unique purpose, to be the leading project tracking solution in Jira, now named Projectrak . Why have we made the change? This decision is not just a name change to give the former Profields a more appropriate name according to what it can do. Profields was born as an app to provide fields to Jira projects. Today Projectrak is much more than that; it has gadgets, different views, integrations with third-party marketplace apps, and more features that enable you to keep track of projects as you have never been able to do with Jira. We are working on a new Cloud version. Stay tuned! Cheers, Leo

            Hi everyone,

             

            At Profields we have just lunch our collaborative backlog where you can suggest ideas, vote other users' ones and be aware about future releases. 

            With your collaboration, we can build a product that fits your needs.

             

            Cheers,

            Laura

            Laura Barreales added a comment - Hi everyone,   At Profields we have just lunch our  collaborative backlog  where you can suggest ideas, vote other users' ones and be aware about future releases.  With your collaboration, we can build a product that fits your needs.   Cheers, Laura

            david added a comment -

            You're welcome Corinne, I think you are the same Corinne I've just answer in our Backlog, aren't you? https://trello.com/c/E2KeQu12

             

            david added a comment - You're welcome Corinne, I think you are the same Corinne I've just answer in our Backlog, aren't you?  https://trello.com/c/E2KeQu12  

            Thanks David. Do you have an expected timeline for this?

            Corinne Scott added a comment - Thanks David. Do you have an expected timeline for this?

            david added a comment -

            Hello Corinne, thank you for your feedback about Profields Cloud, currently the filters are available for the Server version of Profields, is in our plans to also have them on Cloud.

            Cheers,

            David

            david added a comment - Hello Corinne, thank you for your feedback about Profields Cloud, currently the filters are available for the Server version of Profields, is in our plans to also have them on Cloud. Cheers, David

            Unfortunately I have purchased Profields Cloud for this very reason only to find that there is no way to save filters on the navigation screen which includes these additional fields. Such a shame as otherwise the Profields plugin would be a useful tool.

            Corinne Scott added a comment - Unfortunately I have purchased Profields Cloud for this very reason only to find that there is no way to save filters on the navigation screen which includes these additional fields. Such a shame as otherwise the Profields plugin would be a useful tool.

            Hi Jira Server Product Management,

            Please buy Profields and bundle it with future Jira releases.

            Thanks,

            Tom

            Tom Laermans added a comment - Hi Jira Server Product Management, Please buy Profields and bundle it with future Jira releases. Thanks, Tom

            david added a comment -

            Hello Beat, that's exactly what Profields does. Allows you to create a custom field that applies to all project, also being able to config them by schemes and for every project you can set a different value.

            You can also secure the fields and permissions.

            You can find more information here: https://confluence.deiser.com/display/PROFIELDS50/Documentation+Center

            Regards,

            David

            david added a comment - Hello Beat, that's exactly what Profields does. Allows you to create a custom field that applies to all project, also being able to config them by schemes and for every project you can set a different value. You can also secure the fields and permissions. You can find more information here:  https://confluence.deiser.com/display/PROFIELDS50/Documentation+Center Regards, David

            bluescher added a comment -

            I think this is a miss-understanding, no one of the proposed AddOn solves the problem (as I understand).

            I don't want to have field customised for each project.

            I would like to have customised fields for all project where I can insert a different value for each project.

            => Something like a description (text) field where I can fill in a different description for each project, 
            or an integer field where I can set a different project priority for each project. (like Project type, Avatar, Description, Name, ... but a new one and defined from me)

            This field should be visible (if configured) on each issue. Then the developer is able to see on the issue level which issue has higher priority because of the higher priority of the project. It would be possible to prioritise projects, sort them accordingly, reprioritise it, and the priority would always be up to date an each issue. This would be big advantage for shared resources an project plannings with different project managers . 

             

            bluescher added a comment - I think this is a miss-understanding, no one of the proposed AddOn solves the problem (as I understand). I don't want to have field customised for each project. I would like to have customised fields for all project where I can insert a different value for each project. => Something like a description (text) field where I can fill in a different description for each project,  or an integer field where I can set a different project priority for each project. (like Project type, Avatar, Description, Name, ... but a new one and defined from me) This field should be visible (if configured) on each issue. Then the developer is able to see on the issue level which issue has higher priority because of the higher priority of the project. It would be possible to prioritise projects, sort them accordingly, reprioritise it, and the priority would always be up to date an each issue. This would be big advantage for shared resources an project plannings with different project managers .   

            Hi everyone,

            Thank you for your interest in this issue.

            While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

            There are several third party add-ons that solve many of the use cases mentioned here:

            We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, and especially since third party add-ons are available, we've decided to prioritize other areas of the Jira Server roadmap, including:

            • Performance and stability improvements
            • Archiving projects for improved performance
            • Optimising the use of custom fields
            • Improving performance of boards
            • Improving Jira notifications
            • Allowing users to edit shared filters and dashboards
            • Mobile app for Jira Server

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Jira Server Product Management

            SG (Inactive) added a comment - Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  There are several third party add-ons that solve many of the use cases mentioned here: Profields JIRA Metadata Plugin JIRA Project Specific Select Field . We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, and especially since third party add-ons are available, we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management

              Unassigned Unassigned
              e04d28a97289 fbeauregard2
              Votes:
              721 Vote for this issue
              Watchers:
              343 Start watching this issue

                Created:
                Updated: