-
Bug
-
Resolution: Unresolved
-
Low
-
Severity 3 - Minor
-
Jira Software
Issue Summary
When an issue contains Action items in the Description field and the Clone action in Jira automation is used, the newly cloned issue displays the Description field as a Bullet list rather than preserving the original Action items format
Steps to Reproduce
Create an automation as follows:
- <<Manual Trigger>>
- <<For JQL Branch>>
- JQL query : key = xyz-123
- <<Clone Action>>
- Project = Same
- Issue Type = Same
- Summary = CLONE - issue.summary
Expected Results
The Description field should have action items in the cloned issue
Actual Results
The Description field has bullet items in the cloned issue.
The JSON output of the issue shows
"description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-",
This when copied over using {{issue.description}} is converted into bullet items.
Action items are represented as []
Using the Choose field to Set also does not translate [] to action items.
Manual Clone from Issue UI option uses Type taskList as payload to create a Clone.
Visual example:
Currently, there is no known workaround for this behavior. A workaround will be added here when available
[AUTO-1612] Clone action clones an issue with Action items converted into Bullet list
| Description |
Original:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. Visual example: * Original work item: !original.png|thumbnail! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. Visual example: * Original work item: !original.png|thumbnail! * Clone: !clone.png|thumbnail! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. Visual example: h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. Visual example: * Original work item: !original.png|thumbnail! h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
| Attachment | New: original.png [ 505552 ] | |
| Attachment | New: clone.png [ 505551 ] |
| Description |
Original:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. Visual example: h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
We are seeing this same behavior (action items converting to bullets) in a different context. It happens in custom fields of type "Paragraph" when a state transition is executed. It is not consistently repeatable but it has occurred multiple times over the last couple of months. It really destroys the information because you can no longer see what was checked or unchecked - they are all just bullets. We have no workaround - ouch!
| Development Effort | New: L [ 13033 ] | |
| Was this caused by a recent change? | New: Yes, new functionality is broken [ 19130 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
This is a recently introduced functionality in Jira. Note that some of the discussion in the community post relates to how to use the feature with Automation, so there seems to be some customer interest outside of this bug report.
From a quick investigation, it seems as though we might need to use the ADF APIs for both reading the existing issue and creating the new one. (Although it seems documentation for the new `taskList` nodes hasn't been published yet.)
| Description |
Original:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{taslList}* as payload to create a Clone. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{{taskList}}* as payload to create a Clone. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
| Description |
Original:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type {{{taslList}}} as payload to create a Clone. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When an issue contains [Action items|https://community.atlassian.com/t5/Jira-articles/Introducing-Action-items-in-Jira/ba-p/2876018] in the _Description_ field and the _Clone_ action in Jira automation is used, the newly cloned issue displays the _Description_ field as a _Bullet list_ rather than preserving the original Action items format h3. Steps to Reproduce Create an automation as follows: * <<Manual Trigger>> * <<For JQL Branch>> * JQL query : key = xyz-123 * <<Clone Action>> ** Project = Same ** Issue Type = Same ** Summary = CLONE - {{issue.summary}} h3. Expected Results The _Description_ field should have action items in the cloned issue h3. Actual Results The _Description_ field has bullet items in the cloned issue. The JSON output of the issue shows {noformat} "description": "* -Take action 1-\n* -Take action 2-\n* -Take action 3-", {noformat} This when copied over using {{{{{}issue.description{}}}}} is converted into bullet items. Action items are represented as *[]* Using the _Choose field to Set_ also does not translate *[]* to action items. Manual Clone from Issue UI option uses Type *{taslList}* as payload to create a Clone. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
We are experiencing this issue as well. We have test templates and love the action items for walking through a procedure. Unfortunately, when we clone our templates, the action items are replaced by bullets.