Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

New Sub-Task issue type icon not persisting after issue creation

Carl Dotson March 8, 2018

I have project and the PM would like two sub-task options.  The generic Sub-Task with the blue sub-task icon, AND another sub-task titled Defect with a different icon.

You can create either sub-task and select either Defect or Sub-Task and a sub-task is created.  BUT, the resulting sub-task is always being as the Default Sub-task, even if the issue being created was designated as the Defect sub-task

How can I have the resulting issue carry across the correct and corresponding Sub-Task icon and not always default to the Default?

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 15, 2018

Hi Carl,

I believe there are actually a pair of bug tickets about this problem of custom issue types not displaying their icon correctly.  Please see:

for more details.   The later bug ticket appears to have a means to work around this.  It seems that after you change an issue type icon, you might be able to then restart Jira as a means to try to get this change to stick and appear correctly in Jira.

Carl Dotson March 15, 2018

Yep.  Seems to be a caching issue on the server.  We did bounce the server and the correct icon and description are now appearing as desired.

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Atlassian Community Events