Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,296,713
Community Members
 
Community Events
165
Community Groups

Error occurred while storing issue on transition

Edited

Hello Atlassian community,

 

We are currently facing some issues in one of our Jira projects. When any user is trying to transition an issue The following error is thrown

Error occurred while storing issue.

It seems that you have tried to perform an illegal workflow operation.

If you think you shouldn't get this message, please contact your Jira administrators.

The error message suggests that there are some issues in the workflow. But we already checked our workflow that way. There are no conditions, no validators and no post functions in use (expect the automatically generated post functions).

We already created a new workflow from scratch and added it to the project but the issue persists.

Any other Workflow in any other project is working as aspected. 

In the atlassian jira log there can be found these error messages:

Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE public.jiraissue SET pkey=?, issuenum=?, PROJECT=?, REPORTER=?, ASSIGNEE=?, CREATOR=?, issuetype=?, SUMMARY=?, DESCRIPTION=?, ENVIRONMENT=?, PRIORITY=?, RESOLUTION=?, issuestatus=?, CREATED=?, UPDATED=?, DUEDATE=?, RESOLUTIONDATE=?, VOTES=?, WATCHES=?, TIMEORIGINALESTIMATE=?, TIMEESTIMATE=?, TIMESPENT=?, WORKFLOW_ID=?, SECURITY=?, FIXFOR=?, COMPONENT=?, ARCHIVED=?, ARCHIVEDBY=?, ARCHIVEDDATE=? WHERE ID=? (ERROR: current transaction is aborted, commands ignored until end of transaction block)
[...]
Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
[...]
Caused by: org.postgresql.util.PSQLException: ERROR: value too long for type character varying(255)
[...]

Any Help will be highly appreciated

.

Cheers,

Sebastian

2 answers

0 votes

Exactly as @Radek Dostál says, the error 

ERROR: value too long for type character varying(255)

is the problem, but it goes a bit deeper than the workflow.  Something in the workflow process is carrying data that is too long for the database field it is trying to write it to.  It's not necessarily the workflow itself, it's the issue that is the problem.

You can, in theory, persuade a script to do this (in a post function), but it's harder than it sounds because the standard way to write code in a script would actually check the data is compatible.  You can't do it if your scripts are pure Java, but you can do it if you write in Groovy.

Plus, you've already checked for post-functions, so it's not that.

The other way to get this message is to put duff data into a field.  The built-in fields, and custom fields are all coded in a way that stops you doing that (you can't type too many characters into a summary or short text field for example), but

  • it is possible to mess with the code behind the fields to try to be "clever" with them - allowing the summary to be over 254 characters is a minor tweak in a template file for example.
  • There are apps that provide fields that have neglected that validation, and they do pass invalid data into the database read/write functions.

You should check those two possibilities.  The easy thing to do is look at your "system information" page - it will list all the plugins you've added that might be providing a broken field, and there's a section that lists all the files that have been changed away from a standard installation (it will always list an application properties file, but look for any file in that section with a .VM extension, or ones that look field related)

Hmm these are good inputs here.

 

ERROR: value too long for type character varying(255)

This gets me to think the issue itself contains some data in it which does not conform to the jiraissue table (standard text column in postgres is 255 characters so that could be e.g. Summary).

Do you reckon you could attach the issue data via /rest/api/latest/issue/<ISSUEKEY> as .json here? If you need to sanitize it, please do - the only important part is not to change the length of values but we won't care about the summary being "aaaaaa". It's just that I think that something is over allowed length for the table column.

 

If you are absolutely certain that the workflow you are seeing is not just a "draft" (thus the "active" version of the workflow might contain something extra) then that must be something on the issue so we should probably see it in the json I hope.

 

But either way this sounds curious.

Hi Radek,

 

thank you very much for that fast reply. In the attachment you can find the json export.

 

Yes we tested the workflow in another project, there it was working as aspected. Also we just checked that the workflow is not in draft status.

Thank you very much. Cheers,

 

seme

 

{"expand":"renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations","id":"25208","self":"https://xxxx.xxxxx.de/rest/api/latest/issue/25208","key":"EMP-863","fields":{"fixVersions":[],"resolution":null,"customfield_10501":null,"customfield_10900":"","lastViewed":"2022-06-17T13:57:15.001+0200","customfield_10220":null,"priority":{"self":"https://xxxx.xxxxx.de/rest/api/2/priority/4","iconUrl":"https://xxxx.xxxxx.de/images/icons/priorities/low.svg","name":"Low","id":"4"},"labels":[],"customfield_10610":"# XXXXX Office\n- Kein Arbeitsgerät gewünscht\n- Gerät eingegangen\n- Bedarfsabfrage Supervisor\n- Purchase Request eingegangen\n- Abruf aus RV erledigt\n# Onboarding\nXXXXXXXXX\n- Wohnung suchen (optional)\n- Kinderbetreuung (optional)\n- Jobticket\n- Erst-, Brandschutzhelfer:in? Sicherheitsbeauftragte:r?\n- Unterstützung Ausländerbehörde (optional)\n- Unterstützung Bank (optional)\nXXXXX\n- Hardwareabfrage an Supervisor\n- Infos für 1st-day-Mail angefordert (MA aus Ausland: + Welcome Broschüre)\n- Infos für 1st-day Mail erhalten + in Word vorbereitet\n- Digital: DL-Welcomebag erstellt\n- „Vorab-Mail“ mit Info zur Terminvereinbarung mit FO\n- Digital: DL-Welcomebag befüllt\n- Account-Sheet PDF erstellt\n- „Vorab-Mail“ mit Info zur Terminvereinbarung mit FO\n- Info über MA in Welcome Slots eintragen (NUR VERWALTUNG/ FACULTIES / PhDs+PostDocs von Michael Backes)\n- Welcome Slot Termin MA und Vorgesetzen mitteilen (Digital-Variante: Zoom-Meeting)\n- 1 Arbeitstag vor Beginn E-Mail + Link zur DL-Welcomebag\n- Check People Page\nWERKSTUDENTEN\n- Namensettiket f. Welcomebag gedruckt\n- Welcomebag gepackt\n- 1st-Day-Mail in Wiki eintragen\nXXXX\n- Übersicht Ansprechpersonen in Powerpoint-Vorlage personalisieren\n- Auf monatliche Liste für UK setzen wegen Bild für Homepage\n- Zur Buddy Übersicht hinzufügen\n- Buddy bestätigen (vorab mit Führungskraft klären)\n- Herstellung der Kommunikation zwischen Buddy und neuen MA (Vorschlag Zoom Meeting machen)\n- Onboarding-Erste-Woche-Fragebogen verschicken\nXXXXXXXX\n- Onboarding-2 Monats-Feedback koordinieren\nXXXXXX\n- Persönliche Nachricht an neuen MA vorab verschicken + Einladung zum Onboarding Day\nXXXXXX\n- Raumnr. in Jira eintragen\nOTM Team\n- Onboarding-Feedback-Gespräch persönlich oder via Zoom\n# IT\n- EMail-Account created\n- LDAP account created\n- Workplace Equipment: Installation and Basic configuration\n- Special Application Configurations: Outlook, Adobe DC, Teamwire, Jira, ...\n# FO\n- Arbeitsgerät eingegangen (+Datum)\n- Zutrittsmedien vorbereiten (angepasst an Standort)\n- Türschilder prüfen und gegeben falls erneuern\n- LSF Eintrag – nur Lehrende (XXXXXX)\n- Büromaterial bereitlegen\n# Sonstige\n- Arbeitsplatz checken (Möbel + technische Grundausstattung)\n","customfield_10214":null,"customfield_10215":null,"customfield_10216":null,"customfield_10217":null,"customfield_10218":null,"timeestimate":null,"aggregatetimeoriginalestimate":null,"versions":[],"customfield_10615":"{}","customfield_10219":null,"issuelinks":[],"assignee":null,"status":{"self":"https://xxxx.xxxxx.de/rest/api/2/status/10100","description":"","iconUrl":"https://xxxx.xxxxx.de/","name":"Ready For Work","id":"10100","statusCategory":{"self":"https://xxxx.xxxxx.de/rest/api/2/statuscategory/2","id":2,"key":"new","colorName":"blue-gray","name":"To Do"}},"components":[],"customfield_10210":null,"customfield_10211":null,"customfield_10212":null,"archiveddate":null,"customfield_10213":null,"customfield_10203":null,"customfield_10204":null,"customfield_10600":null,"customfield_10205":null,"customfield_10601":null,"customfield_10206":null,"customfield_10602":null,"customfield_10207":null,"customfield_10603":null,"aggregatetimeestimate":null,"customfield_10604":null,"customfield_10208":null,"customfield_10209":null,"customfield_10607":null,"customfield_10608":null,"creator":{"self":"https://xxxx.xxxxx.de/rest/api/2/user?username=admin","name":"admin","key":"admin","emailAddress":"admin@XXXXX.saarland","avatarUrls":{"48x48":"https://xxxx.xxxxx.de/secure/useravatar?ownerId=admin&avatarId=10600","24x24":"https://xxxx.xxxxx.de/secure/useravatar?size=small&ownerId=admin&avatarId=10600","16x16":"https://xxxx.xxxxx.de/secure/useravatar?size=xsmall&ownerId=admin&avatarId=10600","32x32":"https://xxxx.xxxxx.de/secure/useravatar?size=medium&ownerId=admin&avatarId=10600"},"displayName":"XXXXX IT","active":true,"timeZone":"Europe/Berlin"},"subtasks":[],"reporter":{"self":"https://xxxx.xxxxx.de/rest/api/2/user?username=admin","name":"admin","key":"admin","emailAddress":"admin@XXXXX.saarland","avatarUrls":{"48x48":"https://xxxx.xxxxx.de/secure/useravatar?ownerId=admin&avatarId=10600","24x24":"https://xxxx.xxxxx.de/secure/useravatar?size=small&ownerId=admin&avatarId=10600","16x16":"https://xxxx.xxxxx.de/secure/useravatar?size=xsmall&ownerId=admin&avatarId=10600","32x32":"https://xxxx.xxxxx.de/secure/useravatar?size=medium&ownerId=admin&avatarId=10600"},"displayName":"XXXXX IT","active":true,"timeZone":"Europe/Berlin"},"aggregateprogress":{"progress":0,"total":0},"customfield_10200":null,"customfield_10201":null,"customfield_10202":null,"progress":{"progress":0,"total":0},"votes":{"self":"https://xxxx.xxxxx.de/rest/api/2/issue/EMP-863/votes","votes":0,"hasVoted":false},"worklog":{"startAt":0,"maxResults":20,"total":0,"worklogs":[]},"archivedby":null,"issuetype":{"self":"https://xxxx.xxxxx.de/rest/api/2/issuetype/10205","id":"10205","description":"A task that needs to be done.","iconUrl":"https://xxxx.xxxxx.de/secure/viewavatar?size=xsmall&avatarId=10705&avatarType=issuetype","name":"Task","subtask":false,"avatarId":10705},"timespent":null,"project":{"self":"https://xxxx.xxxxx.de/rest/api/2/project/10205","id":"10205","key":"EMP","name":"Employees","projectTypeKey":"business","avatarUrls":{"48x48":"https://xxxx.xxxxx.de/secure/projectavatar?pid=10205&avatarId=10205","24x24":"https://xxxx.xxxxx.de/secure/projectavatar?size=small&pid=10205&avatarId=10205","16x16":"https://xxxx.xxxxx.de/secure/projectavatar?size=xsmall&pid=10205&avatarId=10205","32x32":"https://xxxx.xxxxx.de/secure/projectavatar?size=medium&pid=10205&avatarId=10205"},"projectCategory":{"self":"https://xxxx.xxxxx.de/rest/api/2/projectCategory/10103","id":"10103","description":"","name":"General Management"}},"customfield_11000":null,"customfield_11001":["# XXXXX Office\n- Kein Arbeitsgerät gewünscht\n- Gerät eingegangen\n- Bedarfsabfrage Supervisor\n- Purchase Request eingegangen\n- Abruf aus RV erledigt\n# Onboarding\nXXXXXXXXX\n- Wohnung suchen (optional)\n- Kinderbetreuung (optional)\n- Jobticket\n- Erst-, Brandschutzhelfer:in? Sicherheitsbeauftragte:r?\n- Unterstützung Ausländerbehörde (optional)\n- Unterstützung Bank (optional)\nXXXXX\n- Hardwareabfrage an Supervisor\n- Infos für 1st-day-Mail angefordert (MA aus Ausland: + Welcome Broschüre)\n- Infos für 1st-day Mail erhalten + in Word vorbereitet\n- Digital: DL-Welcomebag erstellt\n- „Vorab-Mail“ mit Info zur Terminvereinbarung mit FO\n- Digital: DL-Welcomebag befüllt\n- Account-Sheet PDF erstellt\n- „Vorab-Mail“ mit Info zur Terminvereinbarung mit FO\n- Info über MA in Welcome Slots eintragen (NUR VERWALTUNG/ FACULTIES / PhDs+PostDocs von Michael Backes)\n- Welcome Slot Termin MA und Vorgesetzen mitteilen (Digital-Variante: Zoom-Meeting)\n- 1 Arbeitstag vor Beginn E-Mail + Link zur DL-Welcomebag\n- Check People Page\nWERKSTUDENTEN\n- Namensettiket f. Welcomebag gedruckt\n- Welcomebag gepackt\n- 1st-Day-Mail in Wiki eintragen\nXXXX\n- Übersicht Ansprechpersonen in Powerpoint-Vorlage personalisieren\n- Auf monatliche Liste für UK setzen wegen Bild für Homepage\n- Zur Buddy Übersicht hinzufügen\n- Buddy bestätigen (vorab mit Führungskraft klären)\n- Herstellung der Kommunikation zwischen Buddy und neuen MA (Vorschlag Zoom Meeting machen)\n- Onboarding-Erste-Woche-Fragebogen verschicken\nXXXXXXXX\n- Onboarding-2 Monats-Feedback koordinieren\nXXXXXX\n- Persönliche Nachricht an neuen MA vorab verschicken + Einladung zum Onboarding Day\nXXXXXX\n- Raumnr. in Jira eintragen\nOTM Team\n- Onboarding-Feedback-Gespräch persönlich oder via Zoom\n# IT\n- EMail-Account created\n- LDAP account created\n- Workplace Equipment: Installation and Basic configuration\n- Special Application Configurations: Outlook, Adobe DC, Teamwire, Jira, ...\n# FO\n- Arbeitsgerät eingegangen (+Datum)\n- Zutrittsmedien vorbereiten (angepasst an Standort)\n- Türschilder prüfen und gegeben falls erneuern\n- LSF Eintrag – nur Lehrende (XXXXXX)\n- Büromaterial bereitlegen\n# Sonstige\n- Arbeitsplatz checken (Möbel + technische Grundausstattung)\n"],"customfield_11002":"0/46","aggregatetimespent":null,"customfield_11003":null,"customfield_10700":null,"resolutiondate":null,"workratio":-1,"watches":{"self":"https://xxxx.xxxxx.de/rest/api/2/issue/EMP-863/watchers","watchCount":1,"isWatching":true},"created":"2022-06-17T13:57:11.698+0200","customfield_10300":null,"customfield_11105":{"self":"https://xxxx.xxxxx.de/rest/api/2/customFieldOption/10700","value":"Open","id":"10700","disabled":false},"customfield_10016":null,"customfield_11106":null,"customfield_10017":null,"customfield_11107":null,"customfield_10018":null,"customfield_11109":null,"updated":"2022-06-17T13:57:13.500+0200","timeoriginalestimate":null,"description":"----\r\nPrimary Affiliation: XXX / External\r\n----\r\n Position: \r\n----\r\nVorname: \r\nNachname: \r\nMale / Female / Divers\r\nPrivate Telefonnummer: \r\nPrivate Email: \r\nSprache: Deutsch / Englisch\r\n----\r\nStandort: \r\nAbteilung: \r\nVorgesetzter: \r\nUDS Mail: \r\n----\r\nVertrag Start: \r\nVertrag Ende: \r\nAccount Ablauf: \r\n----\r\nRaum: \r\nEinrichtung neuer Arbeitsplatz: Ja / Nein\r\nArbeitsgerät: \r\nIT-Ressourcen: ","customfield_10010":null,"customfield_10011":null,"customfield_11100":null,"customfield_11101":null,"customfield_10012":null,"customfield_11102":null,"customfield_10013":null,"customfield_10014":null,"customfield_11103":null,"customfield_11500":null,"timetracking":{},"customfield_11104":1.0,"customfield_10015":null,"customfield_10005":null,"customfield_10006":"{summaryBean=com.atlassian.jira.plugin.devstatus.rest.SummaryBean@3b3a14e5[summary={pullrequest=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@81a0295[overall=PullRequestOverallBean{stateCount=0, state='OPEN', details=PullRequestOverallDetails{openCount=0, mergedCount=0, declinedCount=0}},byInstanceType={}], build=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@3ade8ad0[overall=com.atlassian.jira.plugin.devstatus.summary.beans.BuildOverallBean@620839b4[failedBuildCount=0,successfulBuildCount=0,unknownBuildCount=0,count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], review=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@68749f49[overall=com.atlassian.jira.plugin.devstatus.summary.beans.ReviewsOverallBean@7845623a[stateCount=0,state=<null>,dueDate=<null>,overDue=false,count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], deployment-environment=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@3683ffe8[overall=com.atlassian.jira.plugin.devstatus.summary.beans.DeploymentOverallBean@1565b515[topEnvironments=[],showProjects=false,successfulCount=0,count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], repository=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@5927fe27[overall=com.atlassian.jira.plugin.devstatus.summary.beans.CommitOverallBean@aa0138b[count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}], branch=com.atlassian.jira.plugin.devstatus.rest.SummaryItemBean@2375c188[overall=com.atlassian.jira.plugin.devstatus.summary.beans.BranchOverallBean@1b0015ee[count=0,lastUpdated=<null>,lastUpdatedTimestamp=<null>],byInstanceType={}]},errors=[],configErrors=[]], devSummaryJson={\"cachedValue\":{\"errors\":[],\"configErrors\":[],\"summary\":{\"pullrequest\":{\"overall\":{\"count\":0,\"lastUpdated\":null,\"stateCount\":0,\"state\":\"OPEN\",\"details\":{\"openCount\":0,\"mergedCount\":0,\"declinedCount\":0,\"total\":0},\"open\":true},\"byInstanceType\":{}},\"build\":{\"overall\":{\"count\":0,\"lastUpdated\":null,\"failedBuildCount\":0,\"successfulBuildCount\":0,\"unknownBuildCount\":0},\"byInstanceType\":{}},\"review\":{\"overall\":{\"count\":0,\"lastUpdated\":null,\"stateCount\":0,\"state\":null,\"dueDate\":null,\"overDue\":false,\"completed\":false},\"byInstanceType\":{}},\"deployment-environment\":{\"overall\":{\"count\":0,\"lastUpdated\":null,\"topEnvironments\":[],\"showProjects\":false,\"successfulCount\":0},\"byInstanceType\":{}},\"repository\":{\"overall\":{\"count\":0,\"lastUpdated\":null},\"byInstanceType\":{}},\"branch\":{\"overall\":{\"count\":0,\"lastUpdated\":null},\"byInstanceType\":{}}}},\"isStale\":false}}","customfield_10007":null,"customfield_10008":[],"attachment":[],"customfield_10009":null,"customfield_10801":null,"customfield_10802":null,"summary":"YYYY-MM-DD Name, Firstname (XXXXX / External)","customfield_10000":"0|i01u9k:","customfield_10001":null,"environment":null,"duedate":null,"comment":{"comments":[],"maxResults":0,"total":0,"startAt":0}}}

Hi Radek,

Thank you very much for your fast reply. Sure no problem, you can find the exported json from an issue here: link

 

Furthermore we checked if the te workflow was in draft status ;). Nevertheless we tested it in another project, there it worked as aspected.

 

Thank you very much in advance. Cheers,

 

Sebastian

Thanks!

 

Although I don't see anything in there that would indicate any length errors with jiraissue table.

 

So trying to find something here..

\d jiraissue
                             Table "public.jiraissue"
        Column        |           Type           | Collation | Nullable | Default
----------------------+--------------------------+-----------+----------+---------
 id                   | numeric(18,0)            |           | not null |
 pkey                 | character varying(255)   |           |          |
 issuenum             | numeric(18,0)            |           |          |
 project              | numeric(18,0)            |           |          |
 reporter             | character varying(255)   |           |          |
 assignee             | character varying(255)   |           |          |
 creator              | character varying(255)   |           |          |
 issuetype            | character varying(255)   |           |          |
 summary              | character varying(255)   |           |          |
 description          | text                     |           |          |
 environment          | text                     |           |          |
 priority             | character varying(255)   |           |          |
 resolution           | character varying(255)   |           |          |
 issuestatus          | character varying(255)   |           |          |
 created              | timestamp with time zone |           |          |
 updated              | timestamp with time zone |           |          |
 duedate              | timestamp with time zone |           |          |
 resolutiondate       | timestamp with time zone |           |          |
 votes                | numeric(18,0)            |           |          |
 watches              | numeric(18,0)            |           |          |
 timeoriginalestimate | numeric(18,0)            |           |          |
 timeestimate         | numeric(18,0)            |           |          |
 timespent            | numeric(18,0)            |           |          |
 workflow_id          | numeric(18,0)            |           |          |
 security             | numeric(18,0)            |           |          |
 fixfor               | numeric(18,0)            |           |          |
 component            | numeric(18,0)            |           |          |
 archivedby           | character varying(255)   |           |          |
 archiveddate         | timestamp with time zone |           |          |
 archived             | character(1)             |           |          |

 

// your error sql query

SET
pkey=?,
issuenum=?,
PROJECT=?,
REPORTER=?,
ASSIGNEE=?,
CREATOR=?,
issuetype=?,
SUMMARY=?,
DESCRIPTION=?,
ENVIRONMENT=?,
PRIORITY=?,
RESOLUTION=?,
issuestatus=?,
CREATED=?,
UPDATED=?,
DUEDATE=?,
RESOLUTIONDATE=?,
VOTES=?,
WATCHES=?,
TIMEORIGINALESTIMATE=?,
TIMEESTIMATE=?,
TIMESPENT=?,
WORKFLOW_ID=?,
SECURITY=?,
FIXFOR=?,
COMPONENT=?,
ARCHIVED=?,
ARCHIVEDBY=?,
ARCHIVEDDATE=?
WHERE ID=?

 

pkey -> project.key -> ok

reporter -> reporter.key -> ok

assignee -> assignee(null) -> ok

creator -> creator.key -> ok

issuetype -> issuetype.id -> ok

summary -> summary -> ok (has length of 45)

priority -> priority.id -> ok

resolution -> resolution.id -> ok

issuestatus -> status.id -> ok

archivedby -> archivedby(null) -> ok

 

I do not see anything suspect here. Normally I would say that sounds like a workflow problem. Some sort of automation brute forcing values into something (typically people brutalize the summary). But the issue doesn't currently have a wrong value, so it must be something in the process.

 

Did I understand it right that the error happens with all issues/issuetypes mapped to the workflow, or just a specific issue / specific few?

As you already tried replacing the workflow, I'd try to clone the issue at this point -> diff the json data just for my sanity -> and try the transition again.

But I am not seeing it, either I have missed something from the json/table mapping, or, there is something modifying the issue under your hands when you try the transition, but that sounds a little far fetched as well.

This error happens with all issue(s) + types inside this specific project. Creating new issues or changing the values works fine.

Even any other workflow didn't work.
All other projects are working correctly. 

Also no errors appeared in the Jira integrated database integrity checker.

What custom fields do you have?

Okay so doesn't happen with new issues etc. but does happen even if you change the workflow, so something to do with the issues right now.

Maybe we could fish it up?

Are you able to connect to your postgres and run this?

SELECT CONCAT(p.pkey, '-', ji.issuenum) AS "Issue Key" FROM jiraissue ji JOIN project p ON ji.project = p.id WHERE LENGTH(ji.pkey) > 255 OR LENGTH(ji.reporter) > 255 OR LENGTH(ji.assignee) > 255 OR LENGTH(ji.creator) > 255 OR LENGTH(ji.issuetype) > 255 OR LENGTH(ji.summary) > 255 OR LENGTH(ji.priority) > 255 OR LENGTH(ji.resolution) > 255 OR LENGTH(ji.issuestatus) > 255 OR LENGTH(ji.archivedby) > 255;

 

I would expect to have seen a buggy value from the json earlier though but I guess this is more direct.

 

@Nic Brough _Adaptavist_ I'm ignoring custom fields as I am fixated on the psql error (it complains about jiraissue table specifically). Do you reckon a cf might have something to do with the table though?

@Nic Brough _Adaptavist_ 

In this specific project, no custom fields are used

 

@Radek Dostál 

The error also appears with newly created and older issues.

SELECT CONCAT(p.pkey, '-', ji.issuenum) AS "Issue Key" FROM jiraissue ji JOIN project p ON ji.project = p.id WHERE LENGTH(ji.pkey) > 255 OR LENGTH(ji.reporter) > 255 OR LENGTH(ji.assignee) > 255 OR LENGTH(ji.creator) > 255 OR LENGTH(ji.issuetype) > 255 OR LENGTH(ji.summary) > 255 OR LENGTH(ji.priority) > 255 OR LENGTH(ji.resolution) > 255 OR LENGTH(ji.issuestatus) > 255 OR LENGTH(ji.archivedby) > 255;
Issue Key
-----------
(0 rows)

You won't find it in the database - the whole point is that the data can't be written to it.

You've got a custom field or script or app that is broken.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,598 views 37 46
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you