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

Sprint is nil in Issue #388

Open
Chhekur opened this issue Jul 21, 2021 · 5 comments
Open

Sprint is nil in Issue #388

Chhekur opened this issue Jul 21, 2021 · 5 comments
Labels
needs triage Ticket that needs triage (a proper look for classification)

Comments

@Chhekur
Copy link
Contributor

Chhekur commented Jul 21, 2021

Describe the bug

Sprint is nil in the returned response for Issue

To Reproduce

Provide a link to a live example, or an unambiguous set of steps to reproduce this bug. Include configuration, logs, etc. to reproduce, if relevant.

  1. Hit any of method to get Issue, Get/Search

Expected behavior

Sprint should not be nil at least for Issues which are there in active Sprint

@github-actions
Copy link

Hi! Thank you for taking the time to create your first issue! Really cool to see you here for the first time. Please give us a bit of time to review it.

@andygrunwald
Copy link
Owner

@Chhekur Can you provide the information

  • if you are on Jira on premise or on Jira cloud
  • which jira version
  • A example code snippet

Thank you.

@romeufcrosa
Copy link

I have this same issue

I'm using Jira Cloud (which does not really have the concept of version, so not sure what extra info I could provide regarding that)

As for the code snippet

options := &jira.SearchOptions{
	Expand:     "changelog",
	MaxResults: 100,
	StartAt:    0,
}
query := fmt.Sprintf(
		"project = '%s' AND issuetype in (Bug, Security, Story, Task) AND Sprint in openSprints()",
		projectKey,
	)
result, resp, err := jiraClient.Issue.Search(query, options)

When trying to print the Sprint property for any issue retrieved I get this:
(*jira.Sprint)(<nil>)

@Chhekur
Copy link
Contributor Author

Chhekur commented Nov 19, 2021

@romeufcrosa the main issue over here is, sometimes sprint actually comes under the customfields so you have to parse unknown to get that info.

@andygrunwald andygrunwald added the needs triage Ticket that needs triage (a proper look for classification) label Aug 20, 2022
@andygrunwald
Copy link
Owner

Hey,

I am very sorry that this issue has been open for a long time with no final solution. We work on this project in our spare time, and sometimes, other priorities take over. This is the typical open source dilemma.

However, there is news: We are kicking off v2 of this library 🚀

To provide visibility, we created the Road to v2 Milestone and calling for your feedback in #489

The development will take some time; however, I hope you can benefit from the changes.
If you seek priority development for your issue + you like to sponsor it, please contact me.

What does this mean for my issue?

We will work on this issue indirectly.
This means that during the development phase, we aim to tackle it.
Maybe in a different way like it is currently handled.
Please understand that this will take a while because we are running this in our spare time.

Final words

Thanks for using this library.
If there is anything else you would like to tell us, let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Ticket that needs triage (a proper look for classification)
Projects
None yet
Development

No branches or pull requests

3 participants