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

Unable to transition workflow when app_user.user_key exceeds 60 characters

    XMLWordPrintable

Details

    • 7.01
    • 6
    • Severity 2 - Major
    • 1
    • Hide
      Atlassian Update – 22 October 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will keep the issue open and continue to watch this issue for the further updates.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 22 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will keep the issue open and continue to watch this issue for the further updates. Thank you, Ignat Alexeyenko Jira Bugmaster

    Description

      Summary

      Transitioning an issue will fail if the username of the user transitioning is longer than 60 chars.

      Steps to Reproduce

      1. Create a user whos username is greater than 60 characters
      2. Try to transition any issue within a project

      Expected Results

      The issue should be transitioned successfully

      Actual Results

      The following error message is displayed in a modal window

      Error marking step #10023 finished: root cause: while updating: [GenericEntity:OSCurrentStep][owner,][caller,thisusernameisquitelongandwillbreakworkflowtransitionshowcoolisthathey][dueDate,null][stepId,11][actionId,21][finishDate,2016-09-22 11:37:07.296][id,10023][startDate,2016-09-22 11:16:30.707][entryId,10023][status,Not Done] (SQL Exception while executing the following:UPDATE public.OS_CURRENTSTEP SET ENTRY_ID=?, STEP_ID=?, ACTION_ID=?, OWNER=?, START_DATE=?, DUE_DATE=?, FINISH_DATE=?, STATUS=?, CALLER=? WHERE ID=? (ERROR: value too long for type character varying(60)))
It seems that you have tried to perform an illegal workflow operation.
If you think this message is wrong, please contact your JIRA administrators.

      Along with a message in the logs along the lines of

      2016-08-31 11:23:48,405 http-nio-8080-exec-6 jiraadministrator@atlassianjiraadministrator.com 683x77831x1 admin /secure/WorkflowUIDispatcher.jspa 2ms "UPDATE public.OS_CURRENTSTEP SET ENTRY_ID='24816', STEP_ID='1', ACTION_ID='21', OWNER='', START_DATE='2016-08-31 11:17:56.962', DUE_DATE='null', FINISH_DATE='2016-08-31 11:23:48.402', STATUS='Not Done', CALLER='jiraadministrator@atlassianjiraadministrator.com' make him the scrum master for double 07 'jirasystemadministrator@admin.com' WHERE ID='31979'"
org.postgresql.util.PSQLException: ERROR: value too long for type character varying(60)

      Workaround

      Manually change the column size to varchar(255) on the database or rename the affected user.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-42614 Transitioning issues (adding watchers) fails if the username is longer than 60 characters

          • Low - Low priority issues
          • Gathering Impact

          Activity

            People

              Unassigned Unassigned
              agoncalves Arthur Gonçalves (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: