I have been tasked with ensuring that the data in our work requests are properly completed as well as work request being properly dispositioned. Meaning every month that we close the month in JIRA where all the fields that are suppose to be populated are populated. How do I go about doing this?
Hi @Richard -- Welcome to the Atlassian Community!
Disclaimer: When I see a request like this, I wonder how the information is being used. I suggest investigating that to see what value that info provides.
Okay, how do you define "properly completed" and "properly dispositioned"?
For "properly completed", if you just want to check that there is *any* data in fields, you could check for the converse: missing data in the fields using a saved filter, subscribe, and receive an email monthly. For example, substituting in your project and fields:
project = myProject
AND resolved >= startOfMonth(-1)
AND resolved < startOfMonth()
myField1 IS EMPTY
OR myField2 IS EMPTY
ORDER BY key ASC
This would provide a list of the issues with incomplete information.
Thank you Bill for our prompt response. What I mean by "properly dispositioned" or "properly completed" is "implemented" and "closed" status. What I am doing is running a query using a filter and then downloading to excel then using nested if then statements to find data inconsistencies. In other words we are finding a lot of JIRAs that are not closed or implemented properly. For example if a JIRA is to be closed it must have both implementation data and close date populated. As well as all respective subtasks must be addressed accordingly. And I know that JIRA has the capability of accomplishing this. I just didn't know what the best or most effective and efficient way. Using excel is definitely not the right way. I know that I could probably create a filter that is a nested if then I think. But I was thinking building a dashboard to reflect all my checks. But I'm not sure if that is the best way either.
Thanks for explaining, Richard.
Unfortunately, out-of-the-box Jira does not handle many possible nested queries for parent/child checks. Customers often buy a marketplace add-on for JQL to enhance those features.
For checks on status and the date fields you note, you certainly can test for those with JQL queries. And, you probably can use out-of-the-box dashboard gadgets to visualize some of the information. You may even be able to dynamically build queries for some conditions using the Automation for Jira (A4J) rules to send you reporting.
The key, as often is the case, is in the details of the specific information you want. If you review what you are doing with your spreadsheet and reporting needs, please try to list those use cases, and then the community can give you more concrete ideas about what is/is not possible. Thanks!
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events