Bug, Story and Epic issue types are not part of standardIssueTypes() function results, what is causing this? In the issue navigator, querying this "issuetype in (standardIssueTypes())" is not showing any Bug, Story nor Epic.
There is a bug with the standardIssueTypes() functionality, where if using Issue Types that are an integer they can conflict with the ID of existing Issue Types. This will subsequently cause the JQL function to return improper results.
I raised a bug for this under https://jira.atlassian.com/browse/JRA-31811.
Hmm, could you screen-shot the issue navigator for us? Just a couple of lines showing a bug, story or epic and the column for issue type, key and summary?
This really does sound like a bug though, I've just got a nagging doubt which a picture would completely rule out.
Also, one other wild thought - do you have the "structure" plugin installed? I can't imagine it would be causing this, but it's the only plugin I can think of that might have a reason to affect the navigation filters. (Actually, do you have any 3rd party plugins installed?)
No confidential info in this JSP issue, here is a summary:
Naming a Status or Issue Type as an integer causes problems with the JQL in JIRA, breaking several areas
Status:OPEN (View Workflow)
Fix Version/s: None
Created:01/Mar/13 1:50 AM
Updated:09/Sep/13 11:58 PM
A Status or Issue Type as an integer messes up the way JIRA uses JQL and returns results. This presents in GreenHopper and also in JQL functions such as standardIssueTypes().
Steps to Reproduce
Create a sample issue with a status of "Open".
Search for that issue with the following JQL:
issuekey = DERPIDO-1 and status = 1
issuekey = DERPIDO-1 and status = "1"
Add a status or issue type as an integer, for example 1. This is easy as it conflicts with "Open".
Search again using the above - the behaviour for "1" will change.
This also happens for Issue Types.
JIRA would either:
Present an error about conflicting Status/Issue Types.
Restrict users from being able to create Status/Issue Types that were an integer due to conflicting.
Nothing is returned as there are no issues with a status of "1".
Presented in several places so have raised a bunch of bugs for it.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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!
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