Add null constraint for issuenum column to jiraissue table

XMLWordPrintable

    • 2
    • 20

      Problem Definition

      In some cases due to JSWSERVER-16473 Jira ends up with a NULL value in the issuenum column of jiraissue table,

      Current schema:

                        Table "public.jiraissue"
        Column        |           Type           | Modifiers
----------------------+--------------------------+-----------
 id                   | numeric(18,0)            | not null
 pkey                 | character varying(255)   |
 issuenum             | numeric(18,0)            |
 project              | numeric(18,0)            |
...
Indexes:
    "pk_jiraissue" PRIMARY KEY, btree (id)
    "issue_assignee" btree (assignee)
    "issue_created" btree (created)
    "issue_duedate" btree (duedate)
    "issue_proj_num" btree (issuenum, project)
    "issue_proj_status" btree (project, issuestatus)
    "issue_reporter" btree (reporter)
    "issue_resolutiondate" btree (resolutiondate)
    "issue_updated" btree (updated)
    "issue_votes" btree (votes)
    "issue_watches" btree (watches)
    "issue_workflow" btree (workflow_id)

      Suggested Solution

      Prevent the data consistency problem by adding not null constraint for issuenum column for jiraissue table.

      Workaround

      None

            Assignee:
            Unassigned
            Reporter:
            Andriy Yakovlev [Atlassian]
            Votes:
            15 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated: