Unable to modify Original Estimate field using the /rest/api/2/issue endpoint

[Sara Bardaji]

I am using a script to create and modify issues in Jira. With this script I can set and modify the following fields:

- Priority

- Summary

- Description

- Components

- Labels

- Assignee

- Status

- Parent

- Time Tracking

For the time tracking field I am only working with the original estimate, so when an issue is crated, I set the remaining estimate to the same value as the original estimate and if the issue is modified, I only set the original estimate.

The script seems to be working fine since in one of my projects I am able to crate and modify tasks, including the time tracking field.

However, there is another project in which this isn't working. When I try to modify the time tracking field I get the following error:  {"errorMessages":[],"errors":{"timetracking":"Field 'timetracking' cannot be set. It is not on the appropriate screen, or unknown."}}

I thought that this might be because the time tracking field was not configured in the screen layout for this project, but this is not the case. The time tracking field does appear in the screen layouts.

The only difference I can see between the project in which this works and the project in which it doesn't is that:

- In the first project (in which it works) the screens use only one screen configuration

- In the second project (in which it doesn't work) the screens use two screen configurations, on each for issues of type bug and the other of the rest of the types. Both screen configuration have the time tracking field showing in the layout.

I have no idea of what other difference might be causing this issue. Does anyone know what might be causing this?

[Philipp Sendek]

Hi @Sara Bardaji and welcome to the community!

If the script works on one project but not on another and you've confirmed that the field is on the edit screen of the not-working project, I would have a look at permissions. Maybe the user you're using for the script doesn't have permission to log work in that project?

Alternatively, you could have a look at this answer which solved the same problem in the past: https://community.atlassian.com/forums/Jira-questions/Re-Field-time-tracking-cannot-be-set/qaq-p/1350855/comment-id/627453#M627453
I think you've already checked and applied everything mentioned there, but maybe this still helps.

Let me know if that didn't solve your issue and we'll dig deeper. :-)

Greetings
Philipp

[Sara Bardaji]

Hi @Philipp Sendek , thank you for your answer!

I am using my user to log work in both projects. I guess permissions shouldn't be an issue if I'm able to edit the original estimate directly from Jira right?

Also, I saw the post you mention before posting my question because I went over it and the solution didn't work for me. I double-checked just in case and no luck.

I'm adding screenshots of the screen layouts just in case they help:

I would appreciate some more help with this issue :)

Thank you!

[Sara Bardaji]

Hi again!

I found another difference between the two projects.

In the not-working project, although the Original Estimate field is configured in the edit and and view screens, which according to the screen scheme are the same as the create view, when I try to create an issue directly in Jira, the field doesn't appear. (I'm attaching a screenshot of the create view)

Is it possible that the screen has the field and the layout also, but the create view is showing something different?

[Philipp Sendek]

Hi @Sara Bardaji ,

thanks for the additional info. That sounds quite tricky and is hard to remote-troubleshoot. But when you say that the screen scheme config should cause the create screen to also have the field and it's not there, I would simply assign the correct screen to the create operations in the screen scheme.
Maybe something is off with the configuration and redoing the configuration or doing a direct mapping can help fix that.

Other than that, having ruled out everything else I can think of, I would usually move on to change configurations back and forth (remove field from screen and re-add it, remove field from layout and re-add it, etc.)

P.S.: Regarding your question on permissions: Yes, if you are allowed to adjust the field in the UI, your permissions are fine.

Greetings
Philipp