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.
Join now to unlock these features and more
When using the app "Performance Objectives" i was wondering why i need to create new custom fields and add information to these custom fields by post function on transition? All the information is already present in the project so why creating new custom fields to place the already known information for a second time into.
I want to make a Cycli Time KPI for a project phase called "concept validation" and i want to know for all the projects of 2021 what is the time spent between the date from "created" and "resolved". I thought this would be quite straightforward in selecting data form search for issues and using several filters but when i do that "search for issues" is only showing me present issues. All the past issues are not shown. Is this the raison why the solution for Cycli Time KPI is to maintain this information in custom fields?
I just came across your request here and I believe we've managed to follow up on your query in our support system back at that time.
A new recording was posted recently for the 'Cycle Time KPI' on the website of our app Performance Objectives: Charts for Jira under 'KPI Examples' section that uses 'Time in status' metric and does not rely on new custom fields to gather such events.
To clarify, adding a Jira custom field and updating it with Workflow post function or with 'Jira Automation' is an alternative approach. It helps enrich your Jira data and persists events in the past that may be used in charts and reports on Jira dashboards.
Please let me know if wе can be of further assistance!