JIRA Software 8.20 EOL has been updated to Dec 31st. ... My app shows Oct 19th?

[Matt Olson (old, dont reference)]

Hello all!
It appears that Atlassian updated their JIRA Software (8.20) and JSM (4.20) EOL.

https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html
https://confluence.atlassian.com/jirasoftware/jira-software-8-20-long-term-support-release-change-log-1086401004.html

--------------------------

Documentation previously read October 19th, 2023 as the software version EOL.

Honestly this is great news for a extremely busy work environment such as mine. More time and more breathing room is welcome.

However, my application is still reading the previous EOL date in its Supported Platform health check.

Naturally, I will yield (and insist) upon what Atlassian has officially published. That being said, its enough for confusion and uncertainty. How can I get my JIRA app to refresh / update this to the present information (December 31st)?

[Deleted user]

Hi @Sheri,

 Under custom fields page can you please check if you see both the fields. 

• Epic Name
• Epic Name [deprecated, this field is no longer being used]

If yes, please go to your field configuration of the project and make sure you make "Epic Name" field as required and "Epic Name [deprecated, this field is no longer being used]" field to be optional and then check if you are still getting the same problem.

Regards,

Vijay Ramamurthy

[Sheri]

Hi @[deleted]

Note that I am using the cloud version of Jira. 

Prior to asking my question I went through similar steps to what you suggest above, except that I removed 'Epic Name [deprecated.." from the screen completely. I still received the error. I then tried removing "Epic Name" too, but had the same result. 

I suspect this is some sort of bug.  

I did come up with a work-around - I create the ticket as a story. After creation I am able to change the type to Epic and add the epic name. Seems to work fine. 

Thanks,

Sheri

[Carlos Garcia Navarro]

Hi Sheri,

It appears that there are two fields associated to your screen: "Epic Name" and "Epic Name [deprecated, this field is no longer being used]"). Can you check the screen configuration that is associated to the epic and confirm if these two fields exist and if they are required? If so, then you can change the "Epic Name[deprecated...]" to be optional instead of required. and remove the "Epic Name[deprecated...]" field from the screen configuration. Let me know if you need more details.

Hope it helps,

Carlos

[Sheri]

Hi Carlos, 

Note that I am using the cloud version of Jira. 

I did go through the screen configuration. "Epic Name [deprecated..." shows in the list of available fields, but is NOT being used. I tried removing "Epic Name" from the screen, but even if it is not there I get the error. 

I did come up with a work-around - I create the ticket as a story. After creation I am able to change the type to Epic and add the epic name. Seems to work fine. 

Thanks,

Sheri

[Carlos Garcia Navarro]

Thanks for the info, Sheri. Do you see a label indicating 'required' in the field configuration associated to your screen?:

Carlos