Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-35850

Description field no longer persists when using "Create another"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 6.1, 6.1.1, 6.1.2, 6.1.3
    • None

      I have noticed that others have commented on my previous issues requesting that they be re-opened and also other users have opened new issues regarding this same thing. The Description field should be persisted when using the "Create Another" checkbox. Here is a synopsis of the reasons:

      1. It is easier to clear out the description field than to have to re-type a single word, sentence, paragraph, or section.
      2. If you made the change because the description field is "changed" for each issue, that is correct, it should be changed, however, if you follow that idea to it's conclusion, you should then clear ALL fields since they all need to be reviewed and possibly changed.
      3. This is in direct conflict with the original deployment of the feature and description of the feature as described on the JIRA 5.0 release notes: https://confluence.atlassian.com/display/JIRA/JIRA+5.0+Release+Notes#JIRA5.0ReleaseNotes-customisabledialogbox.

        The Create Issue dialog box allows you to rapidly create a series of related issues with similar options. When you select the Create another check box before clicking the Create button, JIRA creates your issue and automatically pre-populates a new Create Issue dialog box with your previous field values, whilst leaving the Summary field blank. Be aware that any attachments attached to your previously created issue are not carried across by this feature.

      This should be re-addressed and re-released in a more usable fashion if there is going to be a change in the functionality.

      My suggestion would be to default all fields to persist between issue creations, but allow administrators to add fields to a restricted list so that they are cleared between issue creations.

              Unassigned Unassigned
              c1ff22f20cdf Adam Barylak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: