Age of an Idea

Question

Good morning,

I need a way to identify the age of an idea. So far, I was able to create this based on an automation that calculate the created day difference to today and write it to a field.

This brings me a problem, the idea gets updated everyday this automation is run.

Do you have another alternative? Our managers would love to glace and see which ideas are getting old, and at the same time, received a report of what changed this week.

Thank you, Merci,

For reference, where's the automation I have been using:

Abel Lineberger · Answer

I am thinking about a "Staleness" quantification.  Some way to quantify how long an idea has been sitting without interaction.
Should include:

* Date of Creation
* Date of Last Update to include* Status transition
* Addition of comment
* Addition of insight
* Check off of Specification or Design
* Addition of Delivery tickets
* Change in Goal, Goal Impact, Effort, Effort Impact

Best case:

* Should be a number as relevant to all other issues (not completed/in same status) so that we get a relative staleness.  IE This issue is twice as stale as this issue, etc.

Current blockers:

* Updated field cannot be part of a custom equation.

Omer Meshar_0f60qw · Answer

You can always create a view of the ideas sorted by Created, which will show you the ideas by their age (and you can filter out those that are in an already progressing status). This doesn't give you the notion of how old are they, but it does give you the right order of their "age".

Emre Toptancı [OBSS] · Answer

Hello @Martin

Ideas are also represented with Jira issues underneath so anything that works for Jira issues should work for ideas too.

Our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server, Cloud, and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each status. You can do the same for ideas.

You can combine the time for multiple statuses to get metrics like Idea Age.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

Timepiece - Time in Status for Jira

EmreT