La requête #960764 - [JIRA] (GHS-7659) Sprint in openSprints() JQL throws error fornon-admin users a été crée.

Pour effectuer un suivi, et/ou ajouter un commentaire, veuilliez répondre à ce courriel.
Cette requête sera traitée dès que possible.

Merci de votre collaboration,Your request 960764 - [JIRA] (GHS-7659) Sprint in openSprints() JQL throws error fornon-admin users has been created.

For a follow-up, and/or add comments, please reply to this e-mail.
This request will be treated as soon as possible.

Thank you for your cooperation,

Votre requête / Your request
Lisa Marie Lamb commented on GHS-7659 Sprint in openSprints() JQL throws error for non-admin users What is the date for the 6.1.4 release?This message is automatically generated by JIRA.If you think it was sent incorrectly, please contact your JIRA administratorsFor more information on JIRA, see: http://www.atlassian.com/software/jira

Hi lmlamb, 6.1.4 was released on March 6th, but we have had a few releases since then. You can find them here: https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira

Thanks,

What is the date for the 6.1.4 release?

I can dig it. Thanks for the clarification. May have been a better tact to link the other bugs as 'related to'.

This problem together with the linked issues is fixed in the upcoming 6.1.4 release.

All bugs (including this one) had the same root cause, which is the reason why this bug was marked as a duplicate.

This is NOT a duplicate and we're still getting the error. I want to emphasize Jaakko's last comment as we did what Sam describes and it's lowering the value of Jira in the users' eyes... Please fix soon!!

Agree with Matthew J, this is not a duplicate of the issues listed. The behaviour is quite specific and our experience is exactly the same as his. Everything was fine, upgraded GH, no changes made, query breaks for non admins.

I don't think I agree that this is a duplicate of either of the other two issues.

This is something that worked just fine prior to GreenHopper 6.1.3.1 and broke on the upgrade, without changing any other settings or permissions.

GHS-7661: All our users involved absolutely have browse project permissions. This is not the problem in this case.
GHS-7645: The project involved is self-contained and our sprints only contain items from within the same project. This bug is not affecting us.

Global Admins can run these queries, but regular users who were able to run the exact same queries prior to the Greenhopper upgrade are no longer able to do so.

Please consider re-opening this bug as a related but independent bug from the other two. The scenario on those other two bugs are more specific than what this bug actually entails.

This bug results in major loss of functionality in our instance. All dashboard gadgets using openSprints() related queries are broken. Please find a fix soon.

Dashboards are the standard view that most people use to find their issues and check status. I see this is unassigned. Is this in your current sprint? Is there an ETA for a fix?

Please let us know.

Issue still exists in 6.1.3.2. If I construct a query that looks like this:

project = SW AND sprint in openSprints()

I get:

"No issues are assigned to a sprint with id 42"

when logged in as a non-admin user. Admin users can run the query just fine.

Jeff, I felt that issue (GHS-7296) to be the best candidate source of this bug. It seems to alter the way sprints are handled "behind the curtains". Maybe reversing that feature (refactoring) would provide a quick fix before the root cause is fixed.

Jakko, that issues says it was resolved in 6.1.3 but we are all seeing this in 6.1.3.1.

It is the same thing for us. We updated 6.1.0 to 6.1.3.1 last friday.
Attached screenshot.

I think this might be related to GHS-7296.

It is worth noting, that this issue breaks all dashboard gadgets that depend on a saved filter with openSprints() function somewhere in the JQL query.

jira.atlassian.com is also affected by this issue at the moment.

Getting the same results, with No issues are assigned to a sprint with id 1 and No issues are assigned to a sprint with id 8. Sprint ID 1 exists and has issues. Sprint ID 8 doesn't exist in our db at all.

We encountered this issue today after upgrading from 6.1.1 to 6.1.3.1.

Attached screenshot of Ubisoft Error

I have the same problem on one of my installation. project Admin is receiving the error and System admin doesn't.
There is one difference, the error received is :
No issues are assigned to a sprint with id 1
No issues are assigned to a sprint with id 2