If you consider yourself an expert in your field and in Jira, we call on you to join our Stump The Expert Challenge, and earn money for an amazing Robotics Charity that inspires young people to be science and technology leaders and innovators.
All you need to do is provide solutions - using one of the Innovalog products - to any of the below Challenges. They range from quick, every-day Challenges to ultimate mind-benders - the more complex, the higher the donation.
The awards are designed to give anyone an opportunity to participate, but they do require you to be diligent while submitting the solution - see the guidelines below and check out this example. Once our experts review your solution and find it reliable, it will be published, and you will help other Jira Admins to do more with Jira and automate more of their Jira workflows.
There is no limit on the number of entries, but these must be usable, executable use cases that can be implemented using Jira Misc Workflow Extensions (JMWE) or Jira Misc Custom Fields in Jira Server/DC or Jira Cloud instances. And keep in mind that at least once a week we will be removing Challenges that have already received a reliable solution, so don’t delay your entry!
For each answer you submit by January 31st, 2021, and we approve and publish, you will also get one chance to win an Oculus Quest 2!
Review the "small print" below.
FIRST® is more than robots. FIRST is more than STEM. It is a proven game-changer for preparing kids to solve the world’s greatest problems. It inspires young people to be technology leaders and innovators by engaging them in exciting mentor-based programs that build science, engineering, and technology skills.
This cause was recommended to us by Rodney Nissen. Rodney's own experience with FIRST is a must-read!
Answer any of the Challenges from the list below. You can even submit your own. See the guidelines below.
But don't delay - once a solution has been answered, it will no longer be available for submission.
Jira allows you to create custom fields, but what it doesn’t do is give you the ability to create custom fields that will perform calculations. Using JMCF, demonstrate a “work cost estimate” calculation operation, based on a “Cost per Hour” field, a “Number of Hours” field, and a Total field, which will multiply the cost and hours fields.
NOTE: Your submission should be similar in format and details (not necessarily in length) to the example provided here by Roy Klomp.
This $50 Challenge has been answered!
Adding an attachment to a Jira issue is a simple task. However, if you want to validate types of attachments to be added, you'd need to find a workaround.
Using JMWE, validate -- during a workflow transition -- that an attachment that is added to the issue is a Microsoft Excel file and not just any type of file.
This Challenge is closed and the solution will be published soon.
If you have already prepared an answer to this Challenge, submit it for a chance to win an Oculus Quest 2. Otherwise, please pick another Challenge!
This $50 Challenge has been answered!
Jira records transition history; however, displaying who performed a specific transition and making this information readily accessible as an issue field can be done using a workflow function. Using JMWE, show how to create a field that stores who made a particular transition. Display the field in the issue view screen.
(No cheating! JMCF does this out-of-the-box)
This Challenge is closed and the solution will be published soon.
If you have already prepared an answer to this Challenge, submit it for a chance to win an Oculus Quest 2. Otherwise, please pick another Challenge!
To report on KPI's to understand your team's performance, you want to see and report on the time it takes to resolve an issue. Using JMCF, create a "resolution time" field to calculate precisely how much time has elapsed between the date/time the issue was created and the date/time it was resolved. Then, on a dashboard, show the count of issues summarized by the number of days. For example, 4 issues were resolved in one day, 15 issues were resolved in two days, etc.
To see your Total Time to Resolution (TTR), you need to add a pie chart to the dashboard that shows the following information at a glance: the number of issues resolved in under 24 hours, 24 to 72 hours, and 72+ hours, all resolved within the past 30 days. TTR is defined as the time that it takes to resolve an issue after it has been created. Show how to do all of the above using JMCF.
This $50 Challenge has been answered!
In Jira Service Desk, a customer request type needs either a custom field or an attachment. Using JMWE, ensure that if the custom field is left empty, an attachment is required. However, if the field is not empty, no attachment will be required.
This Challenge is closed and the solution will be published soon.
If you have already prepared an answer to this Challenge, submit it for a chance to win an Oculus Quest 2. Otherwise, please pick another Challenge!
A customer submits a support request through the Jira Service Management customer portal. A help desk technician receives the request and classifies it by choosing a Component representing an impacted software application or business area.
They use a second field to select the type of support needed. The type of support available needs to be Component-specific. For example, if the Component is "email," the only applicable support selections are "troubleshooting" and "monitoring." If the Component is "network," the only suitable support selections are "monitoring" and "security." Using JMWE, demonstrate how to prevent a user from choosing an inapplicable support type for the selected Component.
Challenge suggested by:
Rachel Wright, certified Jira Administrator and author of the Jira Strategy Admin Workbook
A JMWE validator is being used during the issue creation step. It validates that the issue has a certain linktype associated with it. The validator works properly when issues are being created. However, it doesn’t work when a user clones an issue in Jira UI - even if the 'clone links' option is selected. Solve the problem by skipping validation when cloning an issue.
Consistency between an issue and its subtasks is important for maintaining your Jira instance's integrity. Using JMWE, demonstrate all of the following:
Challenge suggested by:
Rodney Nissen, The Jira Guy
To ensure consistency between linked issues, you often need to copy information that is being added to related issues during a transition. Using JMWE, demonstrate how to copy all attachments added on the transition screen from the issue to its linked issues.
Often processes require different approvals based on budgets or specific requirements.
Using JMWE, demonstrate how to automatically request approval based on this requirement:
A new issue needs to be automatically assigned to a member of the team (defined as a project role). However, it must be assigned to the least busy team member, i.e. who currently has the least amount of open issues assigned to them. Automate all of the above using JMWE.
For departments that operate based on time zones, it is often necessary to assign issues -- like customer requests -- to a user within a proper group that handles tasks within a specific time frame.
Using JMWE, assign a newly created issue according to the below rules. Note: Assign them all based on a round-robin approach - users will "take turns" within a group.
Challenge suggested by:
Rodney Nissen, The Jira Guy