No, it's a known annoyance. JIRA has several types of "view" for a field, and a field must tell it which views it supports. Obviously, there's a view view, but it's also got edit, xml, search and I think there are some others.
Create, Edit and Transition screens all ask for the "Edit" template for a field.
The read-only custom field in JIRA does not have one, it's only got view, xml and search. So it won't come out on transition screens.
oh well. if I had read the fine print I guess I wouldn't have tried this. transition screen != edit or view screens
Message Custom Field (for edit)
A custom field whose default value will be displayed as HTML or as rendered wiki markup in OnDemand on an 'Edit' screen.
Module cannot be modified
Message Custom Field (for view)
A custom field whose default value will be displayed as HTML or as rendered wiki markup in OnDemand on the 'View' screen.
No, you're going down the right path (although they're turning that add-on off in some places).
The transition screen is an "edit", so a "message custom field (for edit)" will work here. The usual mistake people make here is to not put the message in the field's default value, they use the description!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs