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

Jira issue creation increments issue key counter even if creation fails (producing big gap in issue numbering)

XMLWordPrintable

      Hello,
      following the support request JSP-63263 it seems that the issue key is incremented even if the issue creation fails, this may produce big gaps in issue numbering. I reccomend to increment issue key only when issue creation is succeful.

      How this may happen (according to what experienced in JSP-63263)
      -We have jira configured with create or comment mail handler and "forwardTo" correctly set.
      -At a point we had the smtp server down during three days, so no outgoing mail from Jira.
      -During these period we have recived (at least) one incoming email producing an error at the issue creation time (related to a mySql DB ecoding issue)
      -in this case normally Jira pops the email from the mailbox and sends a "EMAIL HANDLER: Error handling:" notification
      -it seems that being impossible to send the notification (smtp down) jira leaves the incoming email in the mailbox and therefore it tries again one minute after to create the issue, incrementing each time the issue key (I suppose this because if you look at the main gap in JSP-63263 (MMSHD-5757 vs. MMSHD-632) you have ( 5757-632=5125 ) / 1440 (minutes per day) = 3.5 days. That is exactly the duration of the smtp sever downtime.)

      this is very annoyng because for the final user the impression is that the number of issues has explosed and the system is unstable

      I reccomend to increment issue key only when issue creation is succeful.

            [JRASERVER-22110] Jira issue creation increments issue key counter even if creation fails (producing big gap in issue numbering)

            Bugfix Automation Bot made changes -
            Minimum Version New: 4.01
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2845809 ] New: JAC Bug Workflow v3 [ 2928218 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2585542 ] New: JAC Bug Workflow v2 [ 2845809 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1526908 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2585542 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Oswaldo Hernandez (Inactive) made changes -
            Component/s New: Issue Creation - Issue Create Dialog [ 24490 ]
            Component/s Original: Issue Operations [Deprecated] [ 12761 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 664464 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1526908 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v5 [ 647815 ] New: JIRA Bug Workflow w Kanban v6 [ 664464 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v5 [ 266502 ] New: JIRA Bug Workflow w Kanban v6 [ 647815 ]
            Donald Guy made changes -
            Link New: This issue causes JRA-35310 [ JRA-35310 ]

              Unassigned Unassigned
              c234bc3c790a Damiano Migliori
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: