Forums

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

Error While creating a BUG ticket - Date of First Responce and Time in Status

Merili Eeron
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

Hello, 

I have noticed that there has been popping up following error: 

[CHART] Date of First Response: The value of this field cannot be modified as it is set automatically.
[CHART] Time in Status: The value of this field cannot be modified as it is set automatically.

What could they be and how to resolve? 

No settings seem to have been updated. Is it a general Jira error? 

Thank you!  

2 answers

0 votes
Arkadiusz Wroblewski
Community Champion
May 20, 2026

Hello @Merili Eeron 

The error means Jira is actively blocking an attempt to write data to them while the Bug is being created.

Head to Jira settings > Work items > Screens and check the specific Create screen mapped to your Bug issue type. If [CHART] Date of First Response or [CHART] Time in Status are on that screen, go ahead and remove them.

If they aren't on the screen, the conflict is happening somewhere behind. Double-check your field configurations to make sure those fields aren't accidentally set to required. You will also want to verify that an automation rule, a workflow post-function, or an external API payload isn't trying to inject values into them during the creation step.

Here you have small explanation about Fields:

How "[CHART] Date of First Response" and "[CHART] Time in Status" custom fields get migrated between two Jira Cloud site | Migration | Atlassian Support

Merili Eeron
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

@Arkadiusz Wroblewski Thank you for feedback. 

Trying to understand why it happened if we did not update any settings from our end? 

Like Arkadiusz Wroblewski likes this
Arkadiusz Wroblewski
Community Champion
May 20, 2026

@Merili Eeron 

Actually from another angle, when it started ?

Andrew Hayes
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

Getting the same issue here. Seems to have started in the last 24 hours. 

Like Merili Eeron likes this
Merili Eeron
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

Same seems to be here. Issue was not there yesterday and now it is. 

Arkadiusz Wroblewski
Community Champion
May 20, 2026

Hello @Andrew Hayes  and @Merili Eeron @Merili Eeron 

Well, then it is definitely either a regression or an intentional/Not Intentional change. Please open a ticket with Atlassian Support so they can investigate it properly.

One additional thing I found: there is currently only one active Jira-related incident listed, but it is hard to say whether it is connected to your case.

Jira Status

Merili Eeron
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

Could you instruct on where I can open a support ticket with Jira. 

0 votes
Fabio Racobaldo _Catworkx_
Community Champion
May 20, 2026

Hi @Merili Eeron ,

are those fields managed in creation postfunction associate to bug or in any automation?

Fabio

Merili Eeron
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

These are fields in the Jira ticket itself it seems. 

Special fields: 
Screenshot 2026-05-20 154943.png

Suggest an answer

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

Atlassian Community Events