Unfortunately, while this system field is "Navigable", it is not "Orderable". The former makes it possible to see the field in the issue navigator while the latter makes it possible to place it on "screens".
As I understand it, this means that while you can see the field show up in the issue navigator and REST, you cannot get it onto the view issue screen. I suspect that it was just overlooked, but there *could* be some really good reason for this that just doesn't occur to me. My best guess is that this was the simplest way to make sure it couldn't be modified.
I think you should open an improvement request for this.
@Chris Fuller , So was there an improvement request raised for making the creator field "orderable"? If so, I would like to vote/watch if not I would like to raise one. Point me in the direction. Just saying this is kind of half-assed to add this field as only navigable.
The documents bellow may clarify to you, how to configure which field will be shown on which screen:
JIRA doesn't actually have a Creator field, only the Reporter field, which you may edit at any time if you have the necessary permissions.
If you'd like to have a Creator field to know exactly who created the field, you can try Nic's suggestions here .
Hope this helps.
It can be solved as a workaround by SIL script.
Create a custom field Created On with this script:
string fields = getIssueFields(key);
Needs Power Custom Fields plugin: https://marketplace.atlassian.com/apps/1210749/power-custom-fields?hosting=server
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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