You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This is the second part of the Article that I wrote to explain how you can maximize the use of your Atlassian Marketplace apps to increase the Return on Investment and to facilitate the purchase approval process. I used as example one app called Automated Release Notes for Jira and while I explained how to use it, I was identifying hooks that you could use to increase the number of users accessing the app. In this Second part, my focus will be on additional tricks to use the app for more than the original designed scope.
Maximize the power of the templates by adding JQL statements and use filters if needed. Test JQL and filters in the Jira Issue Navigator and then replace it with the ARN Variables.
Consider the use of variables as parameters in your template JQL like projectID or versionName
To trigger a rule you will need to pick at least one version, despite it is used or not in the template. So, if you are generating an Activity report with a JQL statement like the ones below where the variable versionName is not used, you can select any version just to trigger the rule, but the selection won't be considered at all and the reports will be generated in Confluence solely based on the JQL statement
project=[projectId] and resolved >= startOfDay(-30d) ORDER BY IssueType (to obtain all the issues
filter = "T006 - Team - Filter" and resolved >= startOfDay(-30d) and issuetype in (Bug, Escalation,Epic,Task,Story) ORDER BY issueType
I am assuming that in these scenarios you will try to trigger the same rules multiple times to generate your monthly or weekly reports. If that is the case you will need to pay special attention to the variables used on the page name.
[projectName] 30 days activities generated on [timeStamp] where projectName will be always the same but timeStamp will change every time the Rule is generated, this only addition to your page name will avoid the error and it will allow the generation of multiple pages.
Let's say that you are managing multiple teams (30) and you want exactly the same monthly report for each one of them stored in one location, but you don't want to generate 30 actions pointing to 30 different parent pages and you have a Jira project to manage your area where you have full admin access. In addition, you would like to have a choice when the report needs to be generated and eventually generate just a few of them.
Here is the trick
Create a version with each filter name (e.g. "T006 - Team - Filter" - the same filter that contains the projects and that it is used to create team boards)
Change the JQL using filters, but instead of having the name of the filter there, enter the versionName variable. Remember that you need to pick a version to run the rule.
The page name template field includes the variables versionName and timeStamp as parameters, so you need to be careful with the name given to the filter.
Bottom line, we have a choice in how we would like to go from Point A to Point B. I mentioned at the beginning that we are familiar with the Option A, my recommendation would be to try option B and spend more time with your team producing great products and having fun!
By learning how to use this app you will be able to:
I really recommend to try the Option B, you already know option A...
I hope this two-part article provides some ideas in how you can see beyond the description of the app on the marketplace to find ways of adding more users to the application. It is already paid for all of them, try to see how to involve the whole team to generate a comprehensive experience and a compelling reason to invest in the purchase of the app. Be sure that you clearly document any additional usage of the app and train your team accordingly. My best wishes on your Marketplace treasure hunt, there are many hidden gems to be discovered.
To close this article I would like to disclaim that I don't have any commercial affiliation with the developer of the app and what I wrote is based on my experience using the product, please let me know if you find any mistake so I can correct it as soon as possible. And please, don't go without checking this video created by Atlassian to promote one of the previous releases of Jira. Enjoy!!!
Fabian A. Lopez (Community Leader - Argentina, Florida, California)