-
-
Notifications
You must be signed in to change notification settings - Fork 873
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jira Issues seem to be missing "startdate" (i.e. "duedate"'s complement) #1889
Comments
@venthur , I think 'Start Date' isn't a system field and therefore it doesn't translate as a direct attribute of the Issue object; I'd recommend either trying to locate it in the raw payload via the
or via the JIRA fields API:
I imagine it's associated with one of the |
Are you sure it is not a system field? It seems unlikely to me because "start date" and "due date" are both related to the Timeline feature:
I thought custom fields refer to extra (i.e. non system) fields that have been manually created. If that is the case then I don't think "start date" is custom. But following your suggestion, I did find that |
Bug summary
Hi,
querying an issue with set start- and duedates, I only get back issues where "duedate" is correctly set, but "startdate" is completely missing from all the existing fields.
Is there an existing issue for this?
Jira Instance type
Jira Cloud (Hosted by Atlassian)
Jira instance version
No response
jira-python version
3.8.0
Python Interpreter version
3.11
Which operating systems have you used?
Reproduction steps
Stack trace
none
Expected behaviour
startdate exists
Additional Context
No response
The text was updated successfully, but these errors were encountered: