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

Creating issues with the "Create another" checkbox checked, hours should be blank until users fill it

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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.

      When creating issues and/or sub-tasks with the 'Create another' check box checked, the same time that was filled on any time estimating fields is automatically copied to the next issue that will be created.
      These fields should be blank until the user fills them.
      Because if the user doesn't want to estimate time at issue creation time, then he must manually blank it. And if the user forgets to manually blank the field, this field will be wrongly filled.

            [JRASERVER-32877] Creating issues with the "Create another" checkbox checked, hours should be blank until users fill it

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3054661 ] New: JAC Suggestion Workflow 3 [ 3684406 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2605482 ] New: JAC Suggestion Workflow [ 3054661 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2556464 ] New: Confluence Workflow - Public Facing v4 [ 2605482 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2340573 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2556464 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2116427 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2340573 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2076516 ] New: JIRA Bug Workflow w Kanban v6 [ 2116427 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 876444 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2076516 ]
            jonah (Inactive) made changes -
            Description Original: When creating issues and/or sub-tasks with the 'Create another' check box checked, the same time that was filled on any time estimating fields is automatically copied to the next issue that will be created.
            These fields should be blank until the user fills them.
            Because if the user doesn't want to estimate time at issue creation time, then he must manually blank it. And if the user forgets to manually blank the field, this field will be wrongly filled.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-32877].
              {panel}

            When creating issues and/or sub-tasks with the 'Create another' check box checked, the same time that was filled on any time estimating fields is automatically copied to the next issue that will be created.
            These fields should be blank until the user fills them.
            Because if the user doesn't want to estimate time at issue creation time, then he must manually blank it. And if the user forgets to manually blank the field, this field will be wrongly filled.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-32877 [ JRACLOUD-32877 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-cloud

              Unassigned Unassigned
              fwillig Felipevsw (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: