-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
6.3.12, 6.6.0, 6.6.13, 6.6.80, 7.1.0, 6.4.14, 7.2.7, 7.3.1, 7.4.3, 7.6.0, 7.11.2, 8.1.0, 8.2.1, 8.5.0, 8.12.0, 8.14.0, 8.13.2
-
6.03
-
42
-
Severity 3 - Minor
-
60
-
Summary
With workflows created by jira agile the descriptions of the post functions are referencing the java objects instead of the descriptions, please see the attached screenshot.
Environment
- JIRA Software Scrum Default Workflow
Steps to Reproduce
- Select Manage Boards
- Create Board
- Create a Scrumb board
- New project and a new board
- Fill in Board / Project name
- Select *Agile Simplified Workflow (reocmmended)
- Create Board
- Go to workflow for this newly created project
- Select a transition
- check the Post Functions
Expected Results
A description of the post functions.
Actual Results
The following will be processed after the transition occurs
- Type: class
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction
Arguments:
field.name = resolution
field.value =- Type: class
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction- Add a comment to an issue if one is entered during a transition.
- Type: class
Class: com.atlassian.jira.workflow.function.issue.GenerateChangeHistoryFunction- Re-index an issue to keep indexes in sync with the database.
- Type: class
Class: com.atlassian.jira.workflow.function.event.FireIssueEventFunction
Arguments:
eventTypeId = 13
Workaround
For Jira administrator:
- If you need to edit the generated workflow, create your own workflow instead of editing or copying the generated workflow
For system administrator:
- Stop JIRA
- Make sure to backup data just in case
- Fix the descriptor
- For instance:
$ W_ID="10200" # Change this value as the affected workflow ID $ DB_NAME="__JIRA_DATABASE_NAME__" $ psql ... -d ${DB_NAME} -c "Copy (select descriptor from jiraworkflows where id = ${W_ID}) To STDOUT;" > descriptor_${W_ID}.xml # Edit the xml file (Remove '\n' and the redundant line breaks) $ psql ... -c "update jiraworkflows set descriptor = '$(cat descriptor_${W_ID}.xml)' where id = ${W_ID}" ${DB_NAME}
- For instance:
- Start JIRA
- Verify the affected workflow is fixed (Discard the draft workflow if exists)
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Gathering Impact
-
[JSWSERVER-11547] JIRA Agile Simplified Workflow - Post Functions displayed incorrectly
Noticed this in Jira 9 with workflows created by Jira 7.2 or lower
This is annoying, any ideas on root cause? Still finding corrupted workflows in 8.20.1 now.
Oups ... I forgot that Attachment Permission was no more allowed.
Sure that you will be able to find and see theses malformed Workflows !
Soon 7 years that this bug has been raised.
What are you waiting for fixing such bug ?
You have some difficulty to identify the root cause ?
In your source files, I have no idea where you managed it ...
But in the distributed files (here 8.17.0), you will find them in :
- atlassian-jira-software-8.17.0\atlassian-jira\WEB-INF\application-installation\jira-software-application\jira-greenhopper-plugin-8.17.0.jar
In this plugin ...
- The XML Descriptor modules/project-templates.xml defined 4 project-blueprint modules :
-
- basic-software-development-template
- gh-sample-kanban-template
- gh-kanban-template
- gh-scrum-template
- The Enum com.atlassian.greenhopper.service.workflow.SimplifiedWorkflowPresets defines 4 predefined Workflows :
- SIMPLIFIED_WORKFLOW,
- KANBAN_SIMPLIFIED_WORKFLOW,
- KANBAN_SIMPLIFIED_SAMPLE_WORKFLOW,
- BASIC_SOFTWARE_WORKFLOW
When requesting a new project based on a model (example com.pyxis.greenhopper.jira:basic-software-development-template), the project will be created using by the PresetData built by the class com.atlassian.greenhopper.service.workflow.SimplifiedWorkflowServiceImpl for each known templates.
These PresetData references 3 predefined Workflows :
- \templates\greenhopper\jira\workflow\BasicSoftwareDevelopment.xml
- \templates\greenhopper\jira\workflow\GreenHopperKanban.xml
- \templates\greenhopper\jira\workflow\GreenHopperLite.xml
HERE is the needed correction !! These 3 Workflows are not well-formed !!!
The XML Indentation is strangely performed and some extra-characters are present.
It has no effect for OSWorkflow Engine, in charge of interpreting th Workflow descriptor, but it is the root cause of this painful bug when editing the Workflow. A different XML Parser is perhaps used for this 2 distinct features.
IN ALL CASE, YOU HAVE NOW THE FOCUS ON WHERE THE CORRECTION HAS TO BE DONE !!
Note that in the same, it will correct also the Sample Projects created with com.atlassian.greenhopper.sampledata.SampleDataGeneratorImpl.
Please correct it before its birthday !
Vincent
PS : Hopping that this comment will be read not only by Watcher Customers.
3ac924f844ec: Thank you, but the first workaround has already been covered by Alexander Sowatsch, and the second one is only acceptable if you haven't added too much custom transitions that you'd need to recreate or attach temporarily to other statuses.
You can also copy the workflow and remove the statuses and re-add them. Then replace the workflow back to attached workflow.
Hello Everyone,
I have found a workaround and it is working fine without restarting the Jira. All you need to do is to remove the current post-functions and re-add them, it'll fix the issue. I've tested it out. Check the following screenshot for more details.
1: affected post-functions; https://url.upwork.com/_015u5wGVSgtNvW_gP5VN2YgMMJIDg2kmMv
2: updated post-functions; https://url.upwork.com/_015u5wGVSgtNsTnTHbx5QsTrf7zXHoz07Z
I can confirm this affects us as well (Jira DC 8.12.2 and Project Configurator 3.7.3)
I encountered this lately on Jira 8.13.2 - it's a severe bug I cannot see as an administrator until some user notices their workflow is broken and contacts me 
I can second what brevilo writes - same issue with "Project Configurator for Jira" - IT IS a JIRA issue tho.
This is reproducible even on a brand-new Jira instance. You install/clear Jira and it's broken from the outset.
If I export a workflow having this problem as "workflow", and import it again, all postfunction steps with the "broken" formatting are missing.
Similar export/import issue when using "Project Configurator for Jira". All affected post-functions are flagged as broken on import (here for the stock "Software Simplified Workflow" and Jira 8.12.0):
WARNING Message: Postfunction in position 1 in action 11 requires class com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction which is not available. Check if a required workflow plugin is missing. WARNING Message: Postfunction in position 2 in action 11 requires class com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction which is not available. Check if a required workflow plugin is missing. WARNING Message: Postfunction in position 4 in action 11 requires class com.atlassian.jira.workflow.function.issue.GenerateChangeHistoryFunction which is not available. Check if a required workflow plugin is missing. WARNING Message: Postfunction in position 6 in action 11 requires class com.atlassian.jira.workflow.function.event.FireIssueEventFunction which is not available. Check if a required workflow plugin is missing.
Probably needless to say that the reported stock classes aren't missing...
This is not just a trivial cosmetic problem: If I export a workflow having this problem as "workflow", and import it again, all postfunction steps with the "broken" formatting are missing.
So please fix it.
Also, the "remove all \n" workaround does not work for me, or maybe I did not understand it.
Jira v8.11.0 in some projects set and purge resolution doesn't work.
- Type: class
Class: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction
Arguments:
field.name = resolution
field.value =
Jira Software 8.5.1 Data Center - still present
Could you please publish a list of evenTypeId's and their names so we don't have to go select that from the database by hand?
I agree that this BUG has no effect on the expected behavior ... BUT, honestly, each time I have to train users on how to customize their Workflows by using the default Workflows provided by template project, I have some difficulty to explain that it is a known bug, 5 years old.
It is interesting way to explain how Workflow Descriptor is built !
But, which image for your legendary support.
I have just tested it against 8.5.0 ... Always the same,
Please, fix it ...
This issue is still present on Jira Server 7.13.0.
If you're curious what the various eventTypeId numbers stand for, look inside the jiraeventtype table in your database.
Adding an impact to gather.... 
If you decide not to fix this, would you please publish a list of evenTypeId's and their names so we don't have to go select that from the database by hand?
Thank!
Jira 7.6.3
Can replicate this consistently by changing a status to: Allow all statuses to transition to this one
Results in the display changing as described on this issue.
Christopher Mohr
added a comment - Confirmed in JIRA 7.3.4 as well... Hi Atlassians,
Affected Version: JIRA 7.3.1 Server
Occurrence Factor: 100%
please resolve this issue. Its quite annoying, because you can not edit these corrupted post Functions (for example the Fire Event). So you have to delete and recreate the specific post functions (take a look at the scrrenshot). so sad!
Alexander Sowatsch
added a comment - - edited Hi Atlassians,
Affected Version: JIRA 7.3.1 Server
Occurrence Factor: 100%
please resolve this issue. Its quite annoying, because you can not edit these corrupted post Functions (for example the Fire Event). So you have to delete and recreate the specific post functions (take a look at the scrrenshot). so sad!
Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out.
If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it.
Kind regards,
Dong Hoang
JIRA Software
afb6234f8e80 Is the fix only visible in the newly created workflows, or is there some sort of conversion available for the old ones?