Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Include Development Tags in JQL

Brooke Brown
Contributor
November 6, 2018

I am really struggling with our implementation of Jira and Git. I am Product Manager who really needs to see what tickets where deployed and to what environments. The environment information is only available to me in the Development > Tags section of the Jira ticket.  

 

I was successfully able to pull all issues where there has been 1 or more commits:

 

project = <project name> AND development[commits].all > 0 AND development[tags].all ~ "pilotenviro*"

The last portion (bold) is where I am trying to query the dev tags which contain the environments and I am getting a message back from Jira that states:

Available properties are "development[pullrequests]", "development[commits]", "development[reviews]" and "development[builds]"

 

So, I am wondering if there is a way to make development[tags] an available property? Or a better way to accomplish the end goal of listing all issues that have been deployed to an environment and which environment they where deployed to.

Would also like to be able to do a date range on the commits, but I may be pushing the envelope with that piece lol

 

We are using GitHub to manage our deployments.

1 answer

0 votes
Henrique Bittencourt
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 9, 2018

Hi Brooke!

Can you confirm if you're using an add-on to integrate Jira with GitHub?

I'm asking this because the default info provided in the development section are: branch, commit, pull request, but it's when you are using some of the Atlassian Dev Tools, like Bitbucket, Fisheye, Bamboo.

So, for default, the only dev JQL available are:

  • development[pullrequests].all (or .open) 
  • development[commits].all
  • development[reviews].all (or .open)
  • development[builds].failing

So, if there is any way to filter/search using the GitHub tags, is something that plugin's vendor might be more helpful to assist with, (since we don't know how the plugin works at a deep level).

Best Regards

Brooke Brown
Contributor
November 9, 2018

Thanks Henrique! We are using GitHub and Git integration.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events