Can't Retrieve issues according to "Version"

When trying to retrieve according to "Version" (after defining Versions in the new "Agile quick view"), referring to "FixVersion/s" field - the issues are now retrieved.

7 answers

0 vote
Henning Tietgens Community Champion Jun 13, 2013

So what's the question? For JQL searching for Fix Version you have to use fixVersion, for Affected Versions you use affectedVersion.

Henning

No question here, really ...

I had a typo: I meant - the issues are NOT retrieved.

0 vote

Could you expand on this a bit? Maybe post the JQL you are using?

Hi Nic,

If I drag one of the issues to the left pane (titled "Versions"), into the version name called: "OneCalais R6.3"); and then use this term in a JQL filter: ...fixVersion in ("OneCalais R6.3")...

The issue which I dragged to that "Version" is not appearing in the list of answers.

0 vote

Ok, three quick tests; Could you

  • Nip into the issue in Jira (i.e. a Jira issue view, NOT Greenhopper/Agile) and check what it says there?for Fix Version
  • Search for the issue in the simple search screen - not using JQL
  • Check the version tab in the project summary screen

I did some more analysis; this was a bit tricky:

When FixVersion field is "Hidden" (in the associated fields' configuration) - there's no way to retrieve according to "Version" which was associated with the issue in the quick Agile view.

When I configure the "FixVersion" field as "Show" - all works as expected (and one can indeed see the "FixVersion" value reflected properly into the bug details in the "regular jira issue view").

Well, that makes sense - if you've told Jira a field does not exist for a project, then you can't really expect it to return it in searches!

Well, I can argue on that; as it's more related to the interaction between GreenHooper & the basic Jira functionality: if I chose to map issues to versions only by the left pane ("Versions") of the new agile view, and not to manage that mapping anywhere else - I still expect the system to enable retrieving according to that mapping, regardless if the "FixVersion" field is hidden or shown in the "jira issue view" screen!

Remained with the gap I described above.

Hmm. Yes. You hadn't mentioned Greenhopper before.

I'd expect Greenhopper to simply ignore versions (and hence lose functionality) if you hide them from the project.

I'd say this is a bug, worth raising it with Atlassian. Although, I think Jira is working correctly, and as designed, and the problem is actually more that "Greenhopper does stuff that Jira then cannot report on if the fields are hidden"

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

149 views 1 17
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you