You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
There are a lot of layers to this one, so please bare with me.
Everything works great up until the point I try to view the text in a JSD Request type field.
Here's what I have for the Behaviour's value that is passed in the short text field, and you can see that the script file has a green dot, so it's good.
When I create an issue as an Agent (ie in regular Jira view), the text I entered for the default value works when I use \\ as a line break.
However, when the same issue type is created as a request through the JSD portal, I get this:
In summary for characters that (should) create new lines:
Works in Agent View:
Does not work in Portal View:
Does not work in Agent View or Portal View:
Is there any character or character combinations I could use to get a new line in a JSD portal request field by setting the default value through a ScriptRunner Behaviour using a dynamic form short text field with a script?
Thank you in advance!
PS I've got these versions:
JIRA Service Desk Application v4.5.9
ScriptRunner for Jira v6.11.0
I'm not clear on why \\ works in jira.
But I'm pretty sure that there is some escaping going on such that \n is interpreted as \\n etc.
I find that in my testing if you do something like this, it works in both JIRA and JSD:
Hooray! I think it works! :)
in the request type in the portal view
and this in the Agent view
Wow, thank for explaining this so nicely :) Let me check and get back to you.
I tend to be pretty detail oriented. :) I also tend to get a lot of vague Jira tickets and know what it's like to try to answer them. I figure (hopefully!) the better the question, the quicker and better the answer.
Thank you for looking into this for me!