Welcome to the Atlassian Community!
Yes, you could put it in the due date or create a custom field to hold it. What you do with it is up to you to automate - a lot of us create a filter for something like "due next week" and email teams with the results as a reminder, but you can do all sorts of other things with the data.
Hi @M C welcome to the Atlassian Community!
What is your definition of "lead time"? For me, it's not the same as "time limitation".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In addition to what @Nic Brough -Adaptavist- replied, you could also use Releases/Versions as milestones for your Epics.
Add a release date to your version and add it to your Epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @M C 👋
As an alternative , I guess you can try Time in Status for Jira Cloud (developed by my team). With our add-on it is possible to set a lead time/time limitation for epic's
For this you should
Add-on has a 30-day free trial version and free up to 10 users.
Please, let me know if you have any questions
Hope it helps 😌
Valeriia
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @M C
If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center.
Time in Status will help you to see Lead Times easily (including past issues), filter the ones above or below a given time threshold, and see them on your dashboards, if needed.
Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee.
The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.
The Filter option allows you to filter issues below or above a given threshold. So you can easily define a Lead Time column and filter issues where the Lead Time is above X days.
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.
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.
And finally, the app has a REST API so you can get the reports from Jira UI or via REST.
Timepiece - Time in Status for Jira
EmreT
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.