Jan 07, 2019. @Jason Bane As an example, if you want to search for issues created between a date range 1 Jan 2018 to 31 Dec 2018, and want to list them in desceding order by creation date, you can use the below JQL query for your filter: project = "your-project-name" AND created >= "2018-01-01" AND created And we have a different set of status values in the new workflow we’re moving to. For all our existing issues Jira just needs to know how we’re going to map these different status values. What we want is to map like this… Current New TO DO Open IN PROGRESS In Progress Resolved Reopened DONE Closed A few things worth pointing out: 1. Time in Status for Jira Cloud generates a report of how long issues have been staying in a specific status. Concerning your issue - you get the Cycle and Lead Time data by grouping time in statuses. Go to the Status Groups and here you can add New Group or manage existing ones (edit or delete). Also, you can try Time between Statuses, which You can use Enhancer Plugin for Jira 's Time between custom fields for this use case. The Time Between Custom Field calculates the amount of time passed between two statuses/events. It can be configured to work against a specific working calendar as well as excluding paused statuses.

Actual Stages of Bugs in Jira. There are three stages in Jira issue tracking are as follows, 1. Open/Creation/To be done. 2. Work in Progress. 3. Work done/ Closed/ Resolved. The open stage is the stage when the bugs are identified during the testing phase by the testers and are assigned to developers for resolution.

The filters work ok from within Jira for Agents and Administrators etc, and we have created queues for some states - ie Closed Requests. That all works as expected, and only Closed requests are displayed. So I'm confused (as is our customer) as to how, when in the customer portal we select Closed Requests, the queue also includes Resolved ones.
Sx7vx.
  • bend8kaq33.pages.dev/89
  • bend8kaq33.pages.dev/414
  • bend8kaq33.pages.dev/17
  • bend8kaq33.pages.dev/561
  • bend8kaq33.pages.dev/14
  • bend8kaq33.pages.dev/123
  • bend8kaq33.pages.dev/538
  • bend8kaq33.pages.dev/462

    • jira difference between resolved and closed