• 1,946
    • 358
    • 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.

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

      Atlassian Update – April 2023

      Hi everyone,

      As always, thank you for watching, commenting and engaging with us on this ticket. As you might be aware, we’ve gone through a recent re-balancing exercise here at Atlassian to better reflect operating in a changing and difficult macroeconomic environment. As part of the difficult decisions that have been made to prioritise the most critical work for our customers, we’ve had to put this work on pause for the next few quarters.

      In the cases where Issue Templates will provide a suitable workaround - I’m aware of a number of apps (both free and paid) that offer the ability to create templates for different issue types. You can find them here: https://marketplace.atlassian.com/search?product=jira&query=templates

      In terms of silver linings, I’d like to share that we have made progress on investigating and clarifying the requirements and engineering work that is required, so when we are ready to pick this up again, we won't have to go back to zero.

      I know that this is disappointing for many of you, especially in light of the previous update, please accept my sincere thanks for your patience and understanding for this matter.

      Regards,

      Carol

      Update from Nov 2022

      Hi everyone,

      Thank you for your continued engagement on this request. As part of a larger initiative to improve the way fields can be configured, we are planning to bring the ability to configure field contexts for Priority, Description, and potentially other system fields. We have started design work for this and will be onboarding a team to work on it from Q1 next year, and I will provide periodical updates on this ticket.

      We are prioritising the Description field as we have heard from you that it is the most pressing need, but eventually will be extending the support to other system fields once we better understand your use cases for those fields.

      While we’re building this and other improvements to how you configure fields in Jira, we welcome you to join our focus group and work with us to shape the future of configuration in Jira. If you are interested, please email me at clow@atlassian.com and I’ll share more details on the group.

      Regards

      Carol

      Update from November 2021

      Hi everyone,

      Thank you for watching, voting, and commenting on this issue. We understand this has been a long running request. We also understand this has caused a lot of frustration so I don't want to ignore that fact, but I do hope to strike a chord of optimism with this update.

      A recap of the current workarounds:

      (1) Utilising team-managed projects

      1. From your project sidebar, go to Project settings > Issue types.
      2. Select Description and update the default description you want to see when you’re creating an issue.

      (2) Add Description text for a field

      Note: Before you begin, you’ll need to set up a field configuration scheme for your issue types in your project.

      To update the description for the Description field:

      1. Go to Settings > Issues > Field configuration.
      2. Select Field configuration.
      3. Under Actions, select Configure.
      4. Find the Description field, and select Edit.
      5. Update the description for the field 'Description' in the text box.

      The description you add will come up when you create an issue of a certain issue type if it has been associated with the screen. Learn more about associating fields with screens.

      (3) Configure automation rules for your system fields.

      There’s some suggested workflows from other community members in Default text for Description field on Jira Cloud.

      Learn more about automation rules in Jira cloud.

       

      As for building the feature to add default values to system fields in company-managed projects, it is still on our radar.

      For transparency, there’s a number of foundational pieces we are working on in order to unblock this feature. At this stage we hope to be able to start work on this in 12 months - we understand it’s a long time and we ask for your continued patience as we work through the implementation.

      Please continue to vote and in particular please continue to add comments on how your teams find value when using default values for system fields. This feedback on your specific needs and use cases is invaluable for us as we continue to evolve Jira Cloud.

       

      Regards,

      Carol Low
      Product Manager, Jira Cloud

      Original request description

      I would like to provide default values not only for custom, but also for system fields.

      An example:
      Depending on the issue type, I would like to provide different default values for the field "Description" which help users to fill in e.g. the details of a bug issue.

      Workarounds

            [JRACLOUD-4812] Default values of system fields

            1cb3935dd02c here are supported fields : Default Values for 'Create Issue' screen in Jira Cloud - Confluence (atlassian.net)

            1ffb5932be51 and thumbs up : feel free to continue complaining and waiting for a feature expected for 20 years. And keep voting, of course.

            In the meantime you could have used the above feature,

            1. for 2 years already,
            2. for free, and - let me recycle your argument - the editor can potentially continue not to charge, at any point ^^,
            3. in any case, stopping using it tomorrow would have no other consequence than ... not having this native feature ... which is already the case today.

            Julien MALLARD added a comment - 1cb3935dd02c here are supported fields : Default Values for 'Create Issue' screen in Jira Cloud - Confluence (atlassian.net) 1ffb5932be51 and thumbs up : feel free to continue complaining and waiting for a feature expected for 20 years. And keep voting, of course. In the meantime you could have used the above feature, for 2 years already, for free, and - let me recycle your argument - the editor can potentially continue not to charge, at any point ^^, in any case, stopping using it tomorrow would have no other consequence than ... not having this native feature ... which is already the case today.

            0ed2a0cb9a2b Does it really consider any Systemfield, e.g. Environment as well

            Michael Aglas added a comment - 0ed2a0cb9a2b Does it really consider any Systemfield, e.g. Environment as well

            I'm sorry but I'll never swallow a basic functionality forcefully pushed into our throats as a marketplace sale.

            We spend a fortune on Atlassian tools and still have to spend another fortune on plugins?! 

            Even if they are free now - they can start charging at any point, potentially... Also, relying on a 3rd party app for basic functionality is still not right (period).

            Ricardo.Gomes added a comment - I'm sorry but I'll never swallow a basic functionality forcefully pushed into our throats as a marketplace sale. We spend a fortune on Atlassian tools and still have to spend another fortune on plugins?!  Even if they are free now - they can start charging at any point, potentially... Also, relying on a 3rd party app for basic functionality is still not right (period).

            Hi,
            As told by 6f694859ff35 below, the still-free Default Values for 'Create Issue' screen app does the job.
            Very well indeed: we are using it for 2 months and so far so good.

            Thank you Big Fig Tree ! (i'm not related, just grateful)

            Deleted Account (Inactive) added a comment - Hi, As told by 6f694859ff35 below, the still-free   Default Values for 'Create Issue' screen app does the job. Very well indeed: we are using it for 2 months and so far so good. Thank you Big Fig Tree ! (i'm not related, just grateful)

            Only when I see that this is under a board called "astafiej-test" and all hopes disappear......  

            Ciocirlan, Costel-Iulian added a comment - - edited Only when I see that this is under a board called "astafiej-test" and all hopes disappear......  

            Hi @Erki,

            Thank you for trying out Issue Templates Pro - Summary & Description Templates for Jira

            We have fixed the issue you have mentioned and made tons of other improvements in the last few months. Therefore, I would highly recommend giving it another try.

            Feel free to reach out to us if you want a demo 🙏

            Nar Kumar C. - Narva Software added a comment - Hi @Erki, Thank you for trying out Issue Templates Pro - Summary & Description Templates for Jira We have fixed the issue you have mentioned and made tons of other improvements in the last few months. Therefore, I would highly recommend giving it another try. Feel free to reach out to us if you want a demo 🙏

            It's 2024 now, any updates?

            Terry Tsai added a comment - It's 2024 now, any updates?

            NINETEEN YEARS. Atlassian get your priorities straight. You rather build features nobody wants or needs, but the absolute basics like description templates or editing and removing labels are simply ignored.

            "recent re-balancing exercise here at Atlassian to better reflect operating in a changing and difficult macroeconomic environment" what a load of b******. 

            Andreas Evers added a comment - NINETEEN YEARS. Atlassian get your priorities straight. You rather build features nobody wants or needs, but the absolute basics like description templates or editing and removing labels are simply ignored. "recent re-balancing exercise here at Atlassian to better reflect operating in a changing and difficult macroeconomic environment" what a load of b******. 

            Hey team! Any updates on this one?

            Chris Allan added a comment - Hey team! Any updates on this one?

            Hi Team do we have any update?

            Shaik Ameenulla added a comment - Hi Team do we have any update?

            Erki Tammik added a comment - - edited

            I recently tried this free plugin, it might solve problem for many -> Issue Template for Jira - Summary & Description Templates

            I currently have custom description paragraph fields in use in different projects because it hasn't been possible to add templates for the system's "Description" field. This default field has been replaced with the "Bug description" field for some issue types (Bug) to allow adding templates for fields on the create issue screen.

            If someone creates an issue with the wrong issue type and the issue type needs to be changed, it will cause data loss since the destination issue type lacks the "Bug description" field.
            Creating non-standard description fields as a workaround for templates is a bad practice as it only leads to more problems. I'm waiting for better features to keep Jira more standardized; this is one of the features I'm anticipating.

            I don't understand why this issue has not been solved in the past 19 years.

            Erki Tammik added a comment - - edited I recently tried this free plugin, it might solve problem for many -> Issue Template for Jira - Summary & Description Templates I currently have custom description paragraph fields in use in different projects because it hasn't been possible to add templates for the system's "Description" field. This default field has been replaced with the "Bug description" field for some issue types (Bug) to allow adding templates for fields on the create issue screen. If someone creates an issue with the wrong issue type and the issue type needs to be changed, it will cause data loss since the destination issue type lacks the "Bug description" field. Creating non-standard description fields as a workaround for templates is a bad practice as it only leads to more problems. I'm waiting for better features to keep Jira more standardized; this is one of the features I'm anticipating. I don't understand why this issue has not been solved in the past 19 years.

            interesting to see having it in Data Center available for some time, but not in Cloud... thought new feature will be in Cloud first and then somewhen delayed distributed to DC

            Michael Aglas added a comment - interesting to see having it in Data Center available for some time, but not in Cloud... thought new feature will be in Cloud first and then somewhen delayed distributed to DC

            Seems like basic functionality to miss. It's clear that it's on purpose, as it's great to have a marketplace solution, but come on. That's basic as hell. When you create a Bug you have to have some basic guidelines like "repro steps, expected, actual etc."

            Julian Davchev added a comment - Seems like basic functionality to miss. It's clear that it's on purpose, as it's great to have a marketplace solution, but come on. That's basic as hell. When you create a Bug you have to have some basic guidelines like "repro steps, expected, actual etc."

            Team managed supports this but we are Company managed and it is not supported. Not sure why but Yes this would be really nice to have as this would save us creating more custom fields. Definitely be looking for this to be added in soon.

            fjulia@intactinsurance.com added a comment - Team managed supports this but we are Company managed and it is not supported. Not sure why but Yes this would be really nice to have as this would save us creating more custom fields. Definitely be looking for this to be added in soon.

            So I will just leave it here in that situation. Dynamic Forms for Jira --> Default Value and other stuff improving create screen. 

            Jarosław Solecki [Deviniti] added a comment - So I will just leave it here in that situation. Dynamic Forms for Jira --> Default Value and other stuff improving create screen. 

            2363 upvotes and this is put on the back burner.  Seriously?  How many upvotes does Atlassian need before something becomes a priority

            Mark Thompson added a comment - 2363 upvotes and this is put on the back burner.  Seriously?  How many upvotes does Atlassian need before something becomes a priority

            Watching this. Would make life a lot easier.

            Timo Halén added a comment - Watching this. Would make life a lot easier.

            @Carol Low
            When will Atlassian release the feature to have default values for the description field?

            Users are requesting this all the time.

            Erki Tammik added a comment - @Carol Low When will Atlassian release the feature to have default values for the description field? Users are requesting this all the time.

            Templating.app for Jira Cloud might be a good alternative for your use case @Monica

            ... to make sure that every team was able to follow the same standards.

            It allows you to create templates for issues based on an easy UI and it also works with company-managed projects. You can use custom fields and variables to create forms as well. If you have any questions, please feel free to reach out  

            Sarah Schmitt-Bär (Seibert Group) added a comment - Templating.app for Jira Cloud might be a good alternative for your use case @Monica ... to make sure that every team was able to follow the same standards. It allows you to create templates for issues based on an easy UI and it also works with company-managed projects. You can use custom fields and variables to create forms as well. If you have any questions, please feel free to reach out  

            Carol Low added a comment -

            Hi 76bbc6dca166,

            We are still working on the dates, there's been some changes to the teams lately and we are working out the impact to ongoing and planned work. We appreciate your understanding and patience.

            In terms of adding templates - I'm aware of a number of apps (both free and paid) that could potentially be workarounds. You can find them here: https://marketplace.atlassian.com/search?product=jira&query=templates

            From my understanding they should meet the basic need of applying a template for issue creation. Would this be an option for you?

            Regards

            Carol

             

            Carol Low added a comment - Hi 76bbc6dca166 , We are still working on the dates, there's been some changes to the teams lately and we are working out the impact to ongoing and planned work. We appreciate your understanding and patience. In terms of adding templates - I'm aware of a number of apps (both free and paid) that could potentially be workarounds. You can find them here: https://marketplace.atlassian.com/search?product=jira&query=templates From my understanding they should meet the basic need of applying a template for issue creation. Would this be an option for you? Regards Carol  

            Hi @clow@atlassian.com 

            following on "We are prioritising the Description field"  do you have a date for when it will be released? 

            Most of our teams move to company-managed projects to make sure that every team was able to follow the same standards and now we figure it out that is not possible to add a "template" description to our Jira issues, meaning that we will not be able to standardize the described information that's being shared within the teams when opening and moving issues. 

             It will be awesome if you could share some workaround or let us know when this will be implemented so we can manage team's expectations around Jira ways of working. 

             

            Thank you 

            Monica Silva added a comment - Hi @ clow@atlassian.com   following on " We are prioritising the  Description field"   do you have a date for when it will be released?  Most of our teams move to company-managed projects to make sure that every team was able to follow the same standards and now we figure it out that is not possible to add a "template" description to our Jira issues, meaning that we will not be able to standardize the described information that's being shared within the teams when opening and moving issues.   It will be awesome if you could share some workaround or let us know when this will be implemented so we can manage team's expectations around Jira ways of working.    Thank you 

            It's Q1 where is the update? 

            David T Jones added a comment - It's Q1 where is the update? 

            Leon McKay added a comment -

            This ticket is nearly 19 years old and the best hope for realizing the feature are app creators flogging their wares. 

            Atlassian - why are you not responding to this feature request?  Everyone wants/needs it.

            Leon McKay added a comment - This ticket is nearly 19 years old and the best hope for realizing the feature are app creators flogging their wares.  Atlassian - why are you not responding to this feature request?  Everyone wants/needs it.

            I simply want to be able to add a description to the story points field after that field is in use. The description field is there, but no way to add content.

            Larry Allen added a comment - I simply want to be able to add a description to the story points field after that field is in use. The description field is there, but no way to add content.

            Mario Thor added a comment -

            Please try the Cloud version of our Default Values for 'Create Issue' screen app.

            You can set default values for Description (rich text editor included), Summary, Labels, Assignee, Priority fields.

            The app is free. Your feedback is welcome!

            Cheers,
            Mario

             

            Mario Thor added a comment - Please try the Cloud version of our Default Values for 'Create Issue' screen app. You can set default values for Description (rich text editor included), Summary, Labels, Assignee, Priority fields. The app is free. Your feedback is welcome! Cheers, Mario  

            We've also released an app which tackles this request: Summary & Description Templates

            This app also allows you to edit templates and uses a WYSIWYG-Editor for creating templates.

            Unfortunately it is not possible to insert tables or macros e.g. panels yet. And we are still working on supporting team-managed projects. But I'd definitely recommend you to give this app a try

            It's free as well. 

            Looking forward to your feedback.

             

            Sarah Schmitt-Bär (Seibert Group) added a comment - - edited We've also released an app which tackles this request: Summary & Description Templates This app also allows you to edit templates and uses a WYSIWYG-Editor for creating templates. Unfortunately it is not possible to insert tables or macros e.g. panels yet. And we are still working on supporting team-managed projects. But I'd definitely recommend you to give this app a try It's free as well.  Looking forward to your feedback.  

            Hey Nar.

            I tested this feature and there are two important things that are missing:

            1) Feature 1 (must have): Description field should be like this comment input (have possibility to add styles, tables color and etc.) Now it is pure text.
            2) Feature 2 (must have): Ability to edit template - you can't edit template and that's sucks.
            3) Feature 3 (nice to have): Ability to define more templates per issue type (functional bug, or frontend bug, server bug perhaps could have different templates)

            If you could only improve these two first two features, I would say I see lots of potential. Otherwise, now, we cannot use it as it is missing important things we expect to have.

            Do you have any idea if you could work on point 1 and 2? 

            I'm looking forward to hearing from you. 
            Tonka

            Antonija Tadic added a comment - Hey Nar. I tested this feature and there are two important things that are missing: 1) Feature 1 (must have): Description field should be like this comment input (have possibility to add styles, tables color and etc.) Now it is pure text. 2) Feature 2 (must have): Ability to edit template - you can't edit template and that's sucks. 3) Feature 3 (nice to have): Ability to define more templates per issue type (functional bug, or frontend bug, server bug perhaps could have different templates) If you could only improve these two first two features, I would say I see lots of potential. Otherwise, now, we cannot use it as it is missing important things we expect to have. Do you have any idea if you could work on point 1 and 2?  I'm looking forward to hearing from you.  Tonka

            Hi everyone,

            I am happy to let you know we just released an app: Issue Template for Jira.

            You can define custom issue templates for title and description fields, and they will be directly added to respective fields in create issue window.

            It supports both company and team managed projects. The app is currently beta and is free to use. Looking forward to your feedback.

            Regards,
            Nar

            Nar Kumar C. - Narva Software added a comment - - edited Hi everyone, I am happy to let you know we just released an app: Issue Template for Jira . You can define custom issue templates for title and description fields, and they will be directly added to respective fields in create issue window. It supports both company and team managed projects. The app is currently beta and is free to use. Looking forward to your feedback. Regards, Nar

            100% agree with Mark Thompson, Team managed is a poor relation to company managed in many configuration areas, so I find it ridiculous that this is offered as a viable workaround. We have blocked the ability for people to create team managed.

             

            Lynne Ratcliffe added a comment - 100% agree with Mark Thompson, Team managed is a poor relation to company managed in many configuration areas, so I find it ridiculous that this is offered as a viable workaround. We have blocked the ability for people to create team managed.  

            FYI - Team managed projects aren't a viable work around.  There isn't sufficient configuration ability within this type of project in numerous other areas.

            Mark Thompson added a comment - FYI - Team managed projects aren't a viable work around.  There isn't sufficient configuration ability within this type of project in numerous other areas.

            @Itamar Ben Sinai, Many behaviour features are not available on Cloud, will this be changed then at the end of the month?

            Alexander Schoene added a comment - @Itamar Ben Sinai, Many behaviour features are not available on Cloud, will this be changed then at the end of the month?

            Igor,

            in order to have a pre-filled description template, you can use another multiline text field in the create screen and copy the content to the Description field on creating.

            Scriptrunner's Behaviours module  should do that and should be out by the end of this month.

             

             

            Itamar Ben Sinai added a comment - Igor, in order to have a pre-filled description template, you can use another multiline text field in the create screen and copy the content to the Description field on creating. Scriptrunner's Behaviours module  should do that and should be out by the end of this month.    

            I also joined the group. Let’s see how we can get this going. I’m so fed up of adding extra description fields for something so basic.

            Lynne Ratcliffe added a comment - I also joined the group. Let’s see how we can get this going. I’m so fed up of adding extra description fields for something so basic.

            Igor Solovei added a comment - - edited

            May be someone use some kind of pre-filled description field in the task?
            When I create a task, I need the description field to already contain information.

             

            Igor Solovei added a comment - - edited May be someone use some kind of pre-filled description field in the task? When I create a task, I need the description field to already contain information.  

            I joined the group @Radek , let's share it in our networks 😂

            Julien Laffont added a comment - I joined the group @Radek , let's share it in our networks 😂

            @JulienLaffont  - here you go https://www.linkedin.com/groups/9225080/

             

            Radek Dering added a comment - @JulienLaffont  - here you go https://www.linkedin.com/groups/9225080/  

            andre.angelantoni.xk added a comment - - edited

            Well, at this point all hope is lost and

            The <center> cannot hold it is too late.

            See top answer:
            https://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags

            andre.angelantoni.xk added a comment - - edited Well, at this point all hope is lost and The <center> cannot hold it is too late. See top answer: https://stackoverflow.com/questions/1732348/regex-match-open-tags-except-xhtml-self-contained-tags

            Don't panic Andre, they will "begin to work on it" in November 2022 (cf update from the November 2021).

             

            The problem will be solved soon ! (I am targeting November 2023... Or maybe November 2024, but before November 2025 ! (GIEC report asked it) 😂)

            Julien Laffont added a comment - Don't panic Andre, they will "begin to work on it" in November 2022 (cf update from the November 2021).   The problem will be solved soon ! (I am targeting November 2023... Or maybe November 2024, but before November 2025 ! (GIEC report asked it) 😂)

            I think other companies should run ads based on this ticket alone:

            "Want a service offered by a company that actually responds to customer requests?"

            I suppose there is movement now but this will forever be a finalist for the "poorest customer responsiveness ever" award.

            andre.angelantoni.xk added a comment - I think other companies should run ads based on this ticket alone: "Want a service offered by a company that actually responds to customer requests?" I suppose there is movement now but this will forever be a finalist for the "poorest customer responsiveness ever" award.

            Julien Laffont added a comment - - edited

            I think we should create a meetup group : "International Jira users frustrated by the JIRACLOUD-4812 issue"

            It could be funny 😁 

            18 years, this is the age to become an adult in France 😂

             

            Does anybody knows an agile youtuber who could make a video story about this issue ? 

            Maybe one day we can heard about it at the BBC news, 1pm : "Jira, the software which continue to ignore their users since 18 years, but stay the most used Software management system around the world" 🤓

             

            It is good to dream... 

            Julien Laffont added a comment - - edited I think we should create a meetup group : "International Jira users frustrated by the JIRACLOUD-4812 issue" It could be funny 😁  18 years, this is the age to become an adult in France 😂   Does anybody knows an agile youtuber who could make a video story about this issue ?  Maybe one day we can heard about it at the BBC news, 1pm : "Jira, the software which continue to ignore their users since 18 years, but stay the most used Software management system around the world" 🤓   It is good to dream... 

            It seems mind-blowing that such a basic request as default text, for the most important field - in the most important feature - of the most used project tracking software - has been sitting for almost 18!! YEARS. What must happen before this will be implemented? Or is it an inside joke within Atlassian at this point?

            Alexander Schoene added a comment - It seems mind-blowing that such a basic request as default text, for the most important field - in the most important feature - of the most used project tracking software - has been sitting for almost 18!! YEARS. What must happen before this will be implemented? Or is it an inside joke within Atlassian at this point?

            Need this for company-managed projects!

            Robert-Alexandru Oros added a comment - Need this for company-managed projects!

            Exactly, please implement it for Company Managed too. Thanks, K

            Kamil Kubeš added a comment - Exactly, please implement it for Company Managed too. Thanks, K

            This works great for Team-managed projects, please implement it for Company Managed too!

            Italo [Modus Create] added a comment - This works great for Team-managed projects, please implement it for Company Managed too!

            Carol, is there an update on this? It's been about 6 months since the last update. Is there an idea of a timeline for this? Seems this issue is very important to a lot of stakeholders.

            James Paniagua added a comment - Carol, is there an update on this? It's been about 6 months since the last update. Is there an idea of a timeline for this? Seems this issue is very important to a lot of stakeholders.

            Not sure if I am the only one watching the issue because it is hilarious and a great anecdote on users feature suggestions.

            We should maybe start planning for some 20 years celebration for 2024 .

            Jan Scheerer added a comment - Not sure if I am the only one watching the issue because it is hilarious and a great anecdote on users feature suggestions. We should maybe start planning for some 20 years celebration for 2024 .

            I am wondering how many votes are needed to implement this feature?
            Do they need 2 million ? (Because more than 2000 are here).

             

            Dipak Naokar added a comment - I am wondering how many votes are needed to implement this feature? Do they need 2 million ? (Because more than 2000 are here).  

            I am wondering how many votes are needed to implement this feature?
            Do they need 2 million ? (Because more than 2000 are here).

             

            Dipak Naokar added a comment - I am wondering how many votes are needed to implement this feature? Do they need 2 million ? (Because more than 2000 are here).  

            kakomoe added a comment -

            We need this to expand our use of Jira to our business teams too

            kakomoe added a comment - We need this to expand our use of Jira to our business teams too

            toricls added a comment -

            We need this to expand our use of Jira to our business teams

            toricls added a comment - We need this to expand our use of Jira to our business teams

            Dani Lucas added a comment -

            Hi, we need to define templates for "Description" by issuetype and project.

            Dani Lucas added a comment - Hi, we need to define templates for "Description" by issuetype and project.

            I've given up. We're using GitHub Projects (Beta) now rather than Jira.

            Gavin Thomas added a comment - I've given up. We're using GitHub Projects (Beta) now rather than Jira.

            This is (again) one simple thing, which user's need/has needed for several years, but Atlassian does not offer.

            Sari Ollikainen added a comment - This is (again) one simple thing, which user's need/has needed for several years, but Atlassian does not offer.

            JM R. added a comment -

            @Mark Thompson

            > even 17 years later we do still want to do this simple function

            See, that is why they do nothing. People keep the product anyway. They just don't care.

            JM R. added a comment - @Mark Thompson > even 17 years later we do still want to do this simple function See, that is why they do nothing. People keep the product anyway. They just don't care.

              7645729f7e9f Arbaaz Gowher (Inactive)
              37c65ac6191b Frank Schimmel
              Votes:
              2741 Vote for this issue
              Watchers:
              1131 Start watching this issue

                Created:
                Updated: