Hello Everyone,
I have an issue with prepare JQL. I have two different projects in JIRA (one with projects and one with bugs - name it for example PROJ and BUG). I need to find informations with closed PROJ and every different status without status CLOSE for BUG.
In PROJ I have informations about ALL TEH BUGS IN PROJECT and if I have some BUG depends on PROJ I also have an information about it in.
I prepare JQL like this, but I know it isn't prepare properly - but ath the moment I have no idea what can I do more.
project in (BUG, PROJ) and (issuetype = BUG and status != CLOSE) and (issuetype = PROJ and status = CLOSE)
Please help :) If you need more information for my side, please ask.
@Monika Konopska , welcome!
Hi Monika!
You can try structuring the JQL in the following scenario:
Project in (BUG) AND issuetype = BUG AND status != Close OR Project in (PROJ) AND issuetype = PROJ AND status != Close
This is the complete JQL that you can follow to extract the information you need.
Using the OR condition allows Jira to search for the new query value without losing the previous one.
Please try it like this and let me know if it doesn't work.
Hi,
unfortunately it's not working.
It need to be like in for example " issueFunction in issuesInEpics (filter: 77676)" but for project PROJ and poject BUG
I can prepare JQL with closed PROJ and than use it in filter like this above, but I'm not sure how :D Is it possible to match two projects like this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you create separate queries for each of them and get the result you expect?
If you can, you can do them separately and then just unify the queries in a single filter:
Type:
JQL1: Project = XXXX AND issuetype = XXXX AND status = CLOSE
JQL 2: Project = XXXX AND issuetype = XXXX AND status != CLOSE
JQL 3: Project = XXXX AND issuetype = XXXX AND status = CLOSE OR Project = XXXX AND issuetype = XXXX AND status != CLOSE
Save the filter:
Then apply the issuefunction:
issueFunction in issuesInEpics (filter: XXXX)
Understood?
If you can't simulate the scenario, return with a print of the error when performing the query in Jira, maybe then we can help you more soon :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.