I am setting up a single select custom field in JIRA Cloud and the renderers are not available from the Field Configuration Screen.
According to JIRA Cloud documentation, the following renderers are standard (https://confluence.atlassian.com/jiracloud/__renderers-735941878.html):
JIRA currently ships with the following renderers:
The only renderers I see in our instance are when I create a custom text field, are the Default Text Renderer and the Wiki Style Renderer If I create a select list custom field, the renderers don't show at all. I need the other renderers to be available as well.
Has anyone else seen this and have any ideas as to what may be going on?
JIRA is applying appropriate renderers for the fields you are defining. If you add a text field, it offers you one of the two renderers for that. When you add a select list, it gives you the select list renderer because that's the only valid one, it has no other way to draw them. Drawing a select list as text, wiki or even multi-select is nonsense because the data doesn't fit.
I agree that I am getting the correct renderers for text fields. I am not getting any renderers for custom fields that are set up as select lists. I understand that the autocomplete renderer is not available for multi-select lists, but I would at least expect to see the Select List renderer for single select fields. Are you saying that fields that are set up as select lists will not show the Renderers option on the field configuration screen since there is no other renderer option available?
The Atlassian knowledge base does say you can use wiki markup:
But I found that HTML works fine for me, so problem solved.
The documentation says "Note that you can use wiki markup within the field". As others have noted, this is not in fact the case. I can confirm that wiki markup is not rendered in this field (though, oddly enough, HTML is).
Is there something specific in the documentation you were trying to point Richard and others to?
We are also trying to make this exact use case function correctly, but wiki markup is not correctly rendered. Can confirm that no renderers configuration is optioned on the field configuration for this field either. We have fallen back on HTML as well, which is not what we would like.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events