Summary Field Optional Issue

Samuel López February 21, 2023

Hi all, 

I have the following problem, for some reason the Summary field (a non optional field) appears without the * character, and for integrations with Zoom now I have problems because that field (the principal field of the ticket) is missing.

Do you know how could it be solved?

image.png

 

1 answer

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 21, 2023

Hi Samuel - Welcome to the Atlassian Community!

What type of project is this? If Company-managed, check the Field Configuration for that project and issue type for the Summary field to see what it says. 

Samuel López February 21, 2023

Hi,

Well it says team-managed project but I actually have no access to the Field Configuration. I only know that Summary should be a non negotiable field.

image.pngimage.png

Samuel López February 21, 2023

Other than this, I actually don't know how to make it clear to report this issue with my Jira Administrators, I seem uncapable of configure this field Summary.

Do you know if there's an inner configuration that I can report?

Thanks for your help.

Best regards.

Samuel López February 23, 2023

Hi @John Funk 

I've been doing a little more research but not finding any solution yet. All I got this far is that the Field Configuration (at least in de administraition panel in this temporary new server for testing) shows which fields are a Must, but still not getting why this field changed in the real one. 

I'm still checking if I get something else where it may fails but, not success yet.

I would appreciate your commentaries.

Regards.

image.png

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 23, 2023

Sorry for the delay. Yes, Team-managed are different and totally independent from the shared Field Configuration files where you would normally resolve this. 

I would say this is clearly a bug. If this is a new issue type on this project, you might just try deleting it and starting the process again. 

Otherwise, you will probably need to open a support ticket with Atlassian to find out what happened. If you do that, please post the resolution back here - I would love to know what happened.

https://support.atlassian.com/contact/#/

Samuel López May 5, 2023

Hi @John Funk 

I've reported it several time ago, but it was about yesterday or two days ago when I've seen the change applied in the configuration.

Now it's working properly, I imagine they changed the field configuration inside the "system".

I haven't heard from Atlassian about the issue but if I get anything that enlights this up I'd share it here.

Thanks for the support.

Regards.

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 7, 2023

Great! Glad it is working for you!

Abdullah Said
Contributor
November 19, 2024

same old "never be seen again solution" ahh answer

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events