Dear support I have the same issue than @Slava Gefen.

Thank you

Hey, did I understand correctly that wiki style renderer doesn't work for Single line text field but it still presents as an option there?

Is there another Atlassian ticket to remove this not working functionality from single line text fields in field configuration? 😃

Fair enough that you are not going to implement Wiki formatting for a single line field, but can you at least remove the Field Configuration option that allows you to change it to Wiki Markup.  That would be a small change and would avoid confusion.

Hi 5e22f3c7b1cb, would you be able to contact our support team so we can look into this properly for you? thank you 

I've enabled the wiki field renderer for a custom paragraph field and am still unable to see the new renderer.

Field configuration:

Issue screen:

Hi,

Yes it was the wiki renderer was not activated, Thank's.

All that's left is to change all fields and script to use that

Regards,

Rémi de Chalendar

I just tried with Text Field (multi-line) but the result is the same, I still have :

{color:#f6c342} TOLERABLE (R=4) {color}
Is it already available for this field ? If yes how to put bold and color on text please ?

617c7a68cfc7 - let us know if you have any issues

Will check with multi line.
Hope it works.

We're having this issue as well

ETA will be appreciated  Interestingly it works in the dashboard gadgets, but not on the Issue View page

This bug has been open for a while. This is critical for us. What is ETA?

This is not a task; it is a bug. There's the wiki renderer configuration available for text fields. Jira server/DC supports this.. .and  Jira cloud provides exactly the same settings.. and it does not behave as expected.

This is highly relevant if users need to add links to external system to facilitate navigation.

@loretta,
No need to setup a call.

As a user I would like to format a link by entering

[Google|https://google.com]

Resulting in

Google

(Of course the actual link we use is different - it is just an example)

Currently - the single line feed is showing
[Google|https://google.com]

PS - like other users said - it is not working either on multi line fields.

I put it like this, sorry for the layout

	//************* VARIABLES ************* : 
	// Variables
	def resultMap = [:]	// Matrices 
	severityMap = ['10311':1,'10319':1,'10327':1,
					'10312':2,'10320':2,'10328':2,
					'10313':3,'10321':3,'10329':3,
					'10314':4,'10322':4,'10330':4]	
       occurenceMap = ['10315':1,'10323':1,'10331':1,
					'10316':2,'10324':2,'10332':2,
					'10317':3,'10325':3,'10333':3,
					'10318':4,'10326':4,'10334':4]	// Get issue Key
//	def issueKey = 'PTR2-97'
	def issueKey = issue.key	/*
	Fields : 
	Clinical : 
		S customfield_10201
		O customfield_10202
		R customfield_10205
	RGPD
		S customfield_10206
		O customfield_10207
		R customfield_10208
	Software
		S customfield_10209
		O customfield_10210
		R customfield_10211
	*/	//************* MAIN ************* : 
	def calcul_risk (String Sev, String Ocu){
		int risk = severityMap[Sev] * occurenceMap[Ocu]
		def resultMapRisk = [:]
		if (risk in (1..3))
		{
			resultMapRisk.put("color","#14892c")
			resultMapRisk.put("texte","ACCEPTABLE (R=${risk})")
		}
		else if (risk in (4..7))
		{
			resultMapRisk.put("color","#f6c342")
			resultMapRisk.put("texte","TOLERABLE (R=${risk})")
		}
		else if (risk in (8..16))
		{
			resultMapRisk.put("color","#d04437")
			resultMapRisk.put("texte","INNACEPTABLE (R=${risk})")
		}
		return resultMapRisk
	}	//************* MAIN ************* : 
	logger.info("Script start")	//********** Get Issue data
	// Get issue object with fields needed
	def issue = get("/rest/api/3/issue/${issueKey}")
			.queryString('fields','customfield_10201,customfield_10202,customfield_10206,customfield_10207,customfield_10209,customfield_10210')
			.header('Content-Type', 'application/json')
			.asObject(Map)
			.body
	//logger.info("issue : ${issue}")	// Get Fields Map from issue object
	def fields = issue.fields as Map
	//logger.info("fields object : ${fields}")	// Get each field 
	//Clinical : 
	def clinSev_Obj = fields['customfield_10201'] as Map
	def clinOcu_Obj = fields['customfield_10202'] as Map
	//RGPD
	def rgpdSev_Obj = fields['customfield_10206'] as Map
	def rgpdOcu_Obj = fields['customfield_10207'] as Map
	//Software
	def softSev_Obj = fields['customfield_10209'] as Map
	def softOcu_Obj = fields['customfield_10210'] as Map  	if (clinSev_Obj != null && clinOcu_Obj != null)
  	{
  		//*********** Get Values Severity and Occurence
  		String clinSev =  clinSev_Obj.id
  		String clinOcu = clinOcu_Obj.id
//		logger.info("clinSev : ${clinSev}")
//		logger.info("clinOcu : ${clinOcu}")
  		resultMap.put("customfield_10205","*{color:${calcul_risk(clinSev,clinOcu).color}}  ${calcul_risk(clinSev,clinOcu).texte} {color}*")
  		resultMap.put("customfield_10212","${calcul_risk(clinSev,clinOcu).texte}")  	}else
  	{
  		resultMap.put("customfield_10205","")
  		resultMap.put("customfield_10212","")
  	}
  	if (rgpdSev_Obj != null && rgpdOcu_Obj != null)
  	{
  		// Get ids from radio Severity and Occurence
  		String rgpdSev =  rgpdSev_Obj.id
  		String rgpdOcu = rgpdOcu_Obj.id
//		logger.info("rgpdSev : ${rgpdSev}")
//		logger.info("rgpdOcu : ${rgpdOcu}")
  		resultMap.put("customfield_10208","*{color:${calcul_risk(rgpdSev,rgpdOcu).color}}  ${calcul_risk(rgpdSev,rgpdOcu).texte} {color}*")
  		resultMap.put("customfield_10213","${calcul_risk(rgpdSev,rgpdOcu).texte}")
  	}else
  	{
  		resultMap.put("customfield_10208","")
  		resultMap.put("customfield_10213","")
  	}
  	if (softSev_Obj != null && softOcu_Obj != null)
  	{
  	 	// Get ids from radio Severity and Occurence
  	 	String softSev =  softSev_Obj.id
  	 	String softOcu	= softOcu_Obj.id
//	 	logger.info("softSev : ${softSev}")
//	 	logger.info("softOcu : ${softOcu}")
  	 	resultMap.put("customfield_10211","*{color:${calcul_risk(softSev,softOcu).color}}  ${calcul_risk(softSev,softOcu).texte} {color}*")
  	 	resultMap.put("customfield_10214","${calcul_risk(softSev,softOcu).texte}")
  	}	else
  	{
  		resultMap.put("customfield_10211","")
  		resultMap.put("customfield_10214","")
  	}
  	
logger.info("test : ${resultMap}")    
	def result = put("/rest/api/3/issue/${issueKey}")
		.queryString("overrideScreenSecurity", Boolean.TRUE)
		.header('Content-Type', 'application/json')
		.body([
			fields: resultMap		])
		.asString()	if (result.status == 204) {
		return 'Success'
	} else {
		return "${result.status}: ${result.body}"
	}

Hi @remi.dc

 can you share the script which your using, we have some scripts in Jira server and its not working in cloud.

Hi @loretta,

We use it to highlights 3 risk fields, which have 3 level. They are filled by script runner with :
 
ACCEPTABLE
TOLERABLE
INNACEPTABLE

great, thanks for the feedback david.hansen2 and sergei44

Hi @loretta

We use this to get coloured names (as a hyperlink) of linked Job story or Epic which is filled out by Automation and also to get rendered links to related Issues https://drive.google.com/file/d/1IIcdyizH27-QpRe5MnMgII695j62gj7i/view?usp=sharing

Hi @loretta

Yes, this issue is important to our company.   I don't think I need to book time, unless you want to talk about when/how it's going to be fixed.

My use case is simple: I need some sort of basic rendering that would include the ability to mark text as bold, colored, and perhaps include emoji's.   We use a field of this type in our automation to commonly report back automation status and for which we often want to call out attention to something.

Eg,

Automation Status: " ERROR: you must set xyz first"

Note: I have been working on upgrading our automation to use the Jira Rest API v3, so I am fine with using ADF to do this if that helps.

What about this issue !? The new view will be released in few days !
Why this BUG is not already fixed since it exist for a long time ?

Until new view provides single line test field equivalency to old view - this is a release and functionality regression - one of the biggest sins of release and product management  Also, because we are simply talking about a component renderer being broken here, having developed SW, I estimate it will take 1 day for a developer to fix and QA to test. Would be interesting to compare that effort versus all the effort being put into 'managing' this issue. As the saying goes, "we've spent so much time yappin' about this issue it would have been fixed twice and delivered by now"

I have a workaround that can be implemented in zero time - retain old view until this is fixed, and to make business guys happy - retire support for old view on March 31, 2021 as planned - zero cost to Atlassian.

Hi Team,

May I know when the changes will roll out ? our Anchor link is not working in Single Line Text Field(New View).

Thanks,

Parthiban

Any update on whether we are going to have anything that might even remotely remedy this problem when you go and FORCE the new issue view upon us?  Or do we just have to live with unrendered garbage that will be showing up in custom fields?   In my specific case, I would like to provide ADF via the v3 API for our custom single-line fields and be done with this.  Ugh!

Hi Matthew – We’ve used the single text field for all of our external links that are pulled into Confluence using the jira filters - but these no longer work in the new view. CAN YOU PLEASE LET ME KNOW WHO WE CAN BILL OUR TIME TO as our implementation is effectively now broken and my clients don’t want to have to keep paying to find workarounds for all of the things the new issue view has broken. I can’t believe that your update is that this will not be fixed any time in the next four months – and however many months after that when it’s standard functionality in the old view. How can you force users on to the new issue view in March 2021 when you know there will be so many outstanding issues?

Thank you for detailing your use case for using the wiki-style editor in single line text fields. We are working to bring a range of improvements to the new issue view. To be as transparent as possible I wanted to let you know that we will be working on this issue after transitioning all user to the new issue view from 31 March 2021. We will leave this ticket open for you to provide further context until we are able to pick it up after this date.

Non-working text formatting in a text field in a tool which primary purpose is keeping records (i.e. text) after decades of development... it's not even disappointing by now, it's just embarrassing.

Hello, it's not just single line ...

I see the wiki renderer is not applying appropriately in custom multi-line text fields either. I am incredibly disappointed that this fix has been in the works for so long.  

Hi everyone,

My name is Matt, I'm a product manager on the Jira Cloud team. I wanted to provide an update on the situation with this ticket.

Adding wiki rendering to single line text fields is something that we plan to support and is in our long-term backlog. Unfortunately, being in our long-term backlog means that we are unlikely to pick this up in the next 12 months.

Please continue to use the comments section to provide context or ask any questions. Thank you for your continued support.

Kind regards,

Matt

Hi,

Any workaround for this issue? The workaround given is ok when you have a few users to explain how to switch off the new view, but it's a mess when you have hundreds of users....

Any update on this issue? It is creating some headaches for our team. Thanks!

What is the status of this bug, as this prevent us from using new Jira UI.

The issue above doesn't open for me. Can anyone confirm if this has been fixed?

https://getsupport.atlassian.com/browse/PSCLOUD-29431

I am also looking for an update, for what its worth.

Is there any update on this bug?  It is preventing us from using some of the custom field configurations.

This is preventing us from moving across to the new view.

I have a custom field that shows the Visual/Text tab on editing the issue with only a few custom fields selected in the Configure Fields settings:

However, if the Configure Fields setting is changed to include All Fields, then the Visual/Text tabs do not show up on the field. 

Any idea as to why this might be the case?

Hi, Jira Team! 

Thank you for the attention to my bug request.

Use Case 1:
Step 1 https://prnt.sc/k9ryjz\\ Step 2 http://prntscr.com/k9s2rm\\ Result http://prntscr.com/k9s3ts\\ 
Use Case 2:
Add a comment to a Jira ticket http://prntscr.com/k9s5k8\\ Result http://prntscr.com/k9s66u\\ 
Use Case 3:
Edit the ticket description http://prntscr.com/k9s7a5\\ 
And so on... 

I'm expecting prompt resolution.

Cheers,

Stanislav.

This bug is applicable for system fields as well in the new Issue view