Skip to content
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

Open
2 of 4 tasks
venthur opened this issue Aug 27, 2024 · 3 comments
Open
2 of 4 tasks

Comments

@venthur
Copy link

venthur commented Aug 27, 2024

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?

  • I have searched the existing issues

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?

  • Linux
  • macOS
  • Windows

Reproduction steps

1. create an issue with start- and due-date set
2. query this issue with python
3. try to find the start date

Stack trace

none

Expected behaviour

startdate exists

Additional Context

No response

@dimitarOnGithub
Copy link

@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 .raw attribute:

print(issue.raw)

or via the JIRA fields API:

jira = JIRA(<init>)
print(jira.fields())

I imagine it's associated with one of the customfield_ attributes, question is finding out which one.

@venthur
Copy link
Author

venthur commented Aug 28, 2024

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:

Your project’s timeline is a Gantt chart view that can be used to visualize and plan the timing and sequence of individual issues. The schedule bars on the timeline represent the start date and due date of each issue in your project. Schedule bar colors represent the status of each issue.

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 customfield_10015 always contains the start date for all jira tickets I've observed. Is the jira server reporting them as custom or does the Python library translate it into a custom field?

@dimitarOnGithub
Copy link

Are you sure it is not a system field?

I'm almost certain it at least used to; I've personally always seen it as a non-system field, maybe that's changing now, so don't take my word for the 100% truth.

But following your suggestion, I did find that customfield_10015 always contains the start date for all jira tickets I've observed. Is the jira server reporting them as custom or does the Python library translate it into a custom field?

It definitely shouldn't be the JIRA library doing anything to it, but to confirm I imagine you should be able to search for that field in JIRA itself, on my end, custom fields are shown as such via the cf[<integer>]:

search

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants