Versions Compared

Old Version 5

changes.mady.by.user Jeff Turner

Saved on

compared with

New Version 6

changes.mady.by.user Jeff Turner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Excerpt

JIRA 7 bug

Jira
serverAtlassian JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId144880e9-a353-312f-9412-ed028e8166fa
keyJRA-59364
causes most 'Created vs. Resolved Chart' gadgets on dashboards to break with the error:

Invalid field. Valid values are count, cumulative.

Broken portlets can be fixed individually by editing them and setting Collection Operation to either Cumulative (emulating the old default behaviour) or Count:

However only the dashboard owner can do this, and it's not exactly intuitive. This page describes a SQL fix to migrate all Created vs Resolved portlets to the new preference format.

 

Table of Contents

Table of Contents

I haven't yet upgraded. Will I be affected?

...

Code Block
UPDATE sequence_value_item SET seq_id = (SELECT ceil(max(id)/100)*100 FROM gadgetuserpreference) WHERE seq_name='GadgetUserPreference' RETURNING seq_id;
┌────────┐
│ seq_id │
├────────┤
│  12800 │
└────────┘
(1 row)

Shameless Plug

My business, Red Radish Consulting, offers a quarterly JIRA/Confluence upgrade service, and the fix described here was derived on-the-fly for a client. Save yourself the hassle of dealing with exciting bugs like this, and contact us for a quote!