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

      Some users often start logging an issue, but then they realise they need to collate more information.

      What they would like to do is to be able to save what they have as "Draft" (its not visible to anyone else) and they when they have the full information, they can complete and properly submit it.

            [JRASERVER-4233] It would be nice to be able to save issues as "draft"

            ssahu added a comment -

            It would be great to have this feature. 

            ssahu added a comment - It would be great to have this feature. 

            adding support just in case. would love this feature.

            남혜빈/Growth Strategy added a comment - adding support just in case. would love this feature.

            Just lost a lot of work when my PC froze up. Confluence can save as you go, why can't Jira?

            shawn.norman added a comment - Just lost a lot of work when my PC froze up. Confluence can save as you go, why can't Jira?

            Hello, this is a request also shared by our organization

            Simon Ardouin added a comment - Hello, this is a request also shared by our organization

            I agree! We truly need this feature!

            Alejandra added a comment - I agree! We truly need this feature!

            Yaya Li added a comment -

            That's a great idea. We do need a draft feature.

            Yaya Li added a comment - That's a great idea. We do need a draft feature.

            Can we get draft feature, please?

            Corinna Takigawa added a comment - Can we get draft feature, please?

            This would be a great feature to have.  I often log information and build a ticket up separately in my own documentation before finally moving to create the full ticket.  This is necessary to not spam our system with erroneous tickets that end up being merged into others, but is a great waste of time.

             

            Hopefully the tickets could be like regular tickets, visible so the can be organized etc to the user just unpublished and not integrated with the teams flow (maybe can't change state, or has a unique state such as 'draft').

            Aaron Toderash added a comment - This would be a great feature to have.  I often log information and build a ticket up separately in my own documentation before finally moving to create the full ticket.  This is necessary to not spam our system with erroneous tickets that end up being merged into others, but is a great waste of time.   Hopefully the tickets could be like regular tickets, visible so the can be organized etc to the user just unpublished and not integrated with the teams flow (maybe can't change state, or has a unique state such as 'draft').

            Looking forward for such a capability.

            Dror Sivan added a comment - Looking forward for such a capability.

            Goddamn it this really made me angry today.

            https://twitter.com/mreider/status/1590641108950085632

            Reider, Matthew added a comment - Goddamn it this really made me angry today. https://twitter.com/mreider/status/1590641108950085632

              Unassigned Unassigned
              3b1ae0ec93c9 Nick Minutello
              Votes:
              320 Vote for this issue
              Watchers:
              155 Start watching this issue

                Created:
                Updated: