JIRA 7 has landed! Are you an existing JIRA user with questions about upgrading? Visit the Migration Hub for information about upgrading to new JIRA applications

Skip to end of metadata
Go to start of metadata


The following appears in the atlassian-jira.log:


The problem relates to the the sequence value being duplicated for the plugins table.


Test the solution in a development environment prior to implementing in production. The provided solution may for each vary slightly depending on the JIRA instance.

  1. Find out the highest sequence value in the pluginversion table. This can be achieved with the following query:

    It should yield similar results to this:

  2. Increase the table's sequence value to be higher than the highest ID number in your instances table. In this case the highest number was '10051', so to be safe the Sequence ID should be updated to '10070' to give a slight buffer. This can be accomplished through the following query:

    (info) Keep in mind that that the max ID may differ between each JIRA instance. Modify the SEQ_ID number to be higher or lower as needed, but it should always be higher than the max ID in the pluginversion table.



Help us improve!

Is this article helpful?
Is it well written?
Is the content complete?


  1. It would be helpful to indicate how this problem might occur in the first place.

    1. In general this category of errors (sequence value items) often happens due to a manual database insertion job. If there's a different root cause, we'd probably have a hard time tracking it down.

  2. I just got this error when trying to add a custom status to an Agile workflow. I have not done a manual DB insertion. (sad)

    But I'm on OS X, which I know is unsupported. So I only post this as a potential extra data point.