-
Suggestion
-
Resolution: Unresolved
-
35
-
38
-
Hey everyone,
I’m excited to announce that we’ve now opened up signups for the early access program to the new issue transition experience! Learn more about the improvements we’re making and how to sign up for the early access program.
Thanks as always for your patience.
Best,
Arbaaz Gowher
Product Manager, Jira
Issue Summary
The "comment" field into the "Transition screen" appears with the old issue view render, even when we're using the new issue view.
- If we format the comment will appear the markdown code as follows below:
{color:red}test{color}
- If you change the Render from the [Default Render] to [Wiki Style Renderer] this will impact and this should not impact because into the New Jira issue view we're using the "Fabric" render.
Steps to Reproduce
- In the workflow, add a transition screen.
- Transition an issue to this status, to appear the transition screen.
- Type a comment "test" for instance.
- Change the color of the comment to red.
Solution
We need to update the transition screen to use the "Fabric" render instead of the old issue view Render.
- is duplicated by
-
- Closed
- is resolved by
-
- Closed
[JRACLOUD-80133] Comment field on new issue view into the "transition screen" appear with the old issue view render
Good to see that this is in progress 
Our service desk agents are not really capable of wiki markup. Currently, they perform two actions on the issue to transition it:
- Write a comment (to be able to use the wysiwyg editor).
- Trigger the transition.
This means that the customer gets notified twice 
This workaround is terrible, if my project is restricted, by adding the custom field group option, it allows anyone to browse the project.
Great news Arbaaz! It's really an open question why the transition screen wasn't changed to the new rendering screen view.
Will this be implemented only for comments or for all fields?
There is now a very serious and long-standing problem with multiple option selection field too, making the use of this field type impossible on the transition screen, since it does not support the new view.
Is there a deadline for implementation?
Several years have passed since the introduction of the new screen)
It took just 3 years (!!!) for Attlasian to pick this issue. Nice .
(Sarcasm inside)
Great news Arbaaz, we look forward to see this implemented!!
Hey everyone,
We've picked this up and are modernising the Issue Transition experience akin to how we modernised the Issue Create experience a while back. Please watch this ticket for updates!
Additionally, if you'd like to share anything about the current experience or what you expect in the new experience, please feel free to book a time/date here.
Thanks as always for your patience.
Best,
Arbaaz Gowher
Product Manager, Jira Cloud
This issue is really messing with our processes. Please can we get some feedback on it. Every single one of our transition screens has the comment block.
Greetings Atlassian:
Our JSM customers are very frustrated about the different look and feel but also other inconsistencies, two of the most important:
- When you transition, at times, you need to attach a file for the customer: this cannot be done as dropping a file will translate to the path on my hard drive where the file is located. So now in order to attach a file for a status change means that you will need to do it before initiating the transition or after doing it.
- The new canned answers feature cannot be used to comment during transition making the agent work inefficient and at the same time error prone.
This ticket deserves a higher priority and at minimum to be in progress. These are key functionalities that cannot be procrastinated.
Best regards
Claudio Ombrella
Hey everyone,
I’m excited to announce that we’ve now opened up signups for the early access program to the new issue transition experience! Learn more about the improvements we’re making and how to sign up for the early access program.
Thanks as always for your patience.
Best,
Arbaaz Gowher
Product Manager, Jira