Emre Toptancı [OBSS] Atlassian Partner

Comments

  • Hello @Administrador de Jira GA , SLA timers essentially measure the time between two points in issue history and those two points are usually when the issue transitions to a status. So it is (once again usually) possible to see it as the total time spent on one or more statuses. The solution I am proposing below does not…
    in How can I get the total average of a series of SLA's. Comment by Emre Toptancı [OBSS] April 2021
  • Prueba Time in Status by OBSS Timepiece - Time in Status for Jira EmreT
    in Como extrair o Lead Time no Jira? Comment by Emre Toptancı [OBSS] April 2021
  • Hello Alexander, The admin can set the Search Template to None and prevent searches. That is no problem. What I want is to make that None value, default. When the admin creates a new custom field of my type, the selected Search Template should be None by default.
    in How to set the default Search Template for my custom field type to None Comment by Emre Toptancı [OBSS] April 2021
  • OK, I guess I figured out how it works. The approval process works based on the workflow definition of the time the issue is created. If you change the workflow definition and ... * add approval * or change the user field used for approval ... existing issues are not affected. Only new issues respect the new definition.…
    in Approvals in service desk show as "No approvers selected" when approver field is populated Comment by Emre Toptancı [OBSS] April 2021
  • Hello @Akshay Aggarwal Our team at OBSS built Time in Status for this exact need. 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 so you can see status times for each status separately. You can combine statuses in any way…
    in How to write a JQL to list issues whose status is not changed to the next within 10 minutes? Comment by Emre Toptancı [OBSS] April 2021
  • Hello @Bret Spangenberg , Control chart is prepared based on issue history records (which you can see in History tab of each issue's view screen) and editing them is not possible. I should also note that control chart is very limited in terms of flexibility. It draws the overall picture but does not give you a lot of…
    in Epic Cycle Time fields and calculation Comment by Emre Toptancı [OBSS] April 2021
  • Hello @Tara Woodham , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. It also has reports…
    in Transition to status not increasing Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Joey Klein , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. You can combine…
    in Average time to resolution by assignee Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Gajanan Sasane , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. The recently…
    in JQL to find all the issues which are closed within 3 days of creation of the ticket Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Vaibhav Patki , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. You can combine…
    in How to create Aging Report in JIRA Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Bud Herz , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. You can combine statuses…
    in Who changed the status? Comment by Emre Toptancı [OBSS] March 2021
  • Hello Alexey, For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. You can combine statuses…
    in Time is status data Comment by Emre Toptancı [OBSS] March 2021
  • Hello @ssampson , For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status. 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 or assigned to each assignee. You can combine statuses…
    in Average Time in Status Gadget Set-up Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Nitin S. Joshi , Jira does not give built-in flexible reporting options about this. You can try getting the history data either directly from database or REST API to calculate this yourself. You can also use some workflow functions to implement custom measurements but will probably be hard to maintain. For a ready…
    in Getting the time between an issue is In-Progress to Closed Comment by Emre Toptancı [OBSS] March 2021
  • Hello @dan.laasnareuter , If you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status has reports that show you how many times each status or each transition was used for each issue (It also allows you…
    in Measure Rework by transition status Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Deepanshu Natani , If you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status does not introduce a custom field or a custom field type to your system but it can display its output in its own…
    in Create calculated custom field to track time in a particular status Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Samuel Prathipaty , If you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can combine…
    in Suggest the Add-ons for the following requirements. Comment by Emre Toptancı [OBSS] March 2021
  • Hello @harsha vardhan , The average age report is not very explicit about how it calculates those values. My team at OBSS built Time in Status app. The app shows how much time each issue spent in each status. You can also group those issues to get averages based on dates and other issue fields. I believe you can use Time…
    in Average Age report Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Chris Miller , Our team at OBSS built Time in Status app for similar needs. Its date reports might help you with that. TiS is available for Jira Server, Cloud and Data Center. Mainly, Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. It also has 4 types of…
    in Is there a Started or start date and end/complete field in the baseline fields for Jira Datacenters? Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Gui Ávila , We also connected with you through our support channel but for those other who come by this question in the future, I would like to leave an answer. For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira…
    in Time spent for QA Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Carlo Lynch , For a ready built solution that offers great fexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. ( @Bill Sheboy , I would hate to disappoint you :D ) Time in Status allows you to see how much time each issue…
    in Control Chart & Paused Work w/ Flags Comment by Emre Toptancı [OBSS] March 2021
  • Hello @julio valdez , For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. Of…
    in JIRA - on-hold average time tickets Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Gajanan Sasane , For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Mainly, Time in Status allows you to see how much time each issue spent on each status or assigned to…
    in Need report for how many time we transit to particular status Comment by Emre Toptancı [OBSS] March 2021
  • Hello @Alessandro Gurgel , Our team at OBSS built Time in Status app for similar needs. Its date reports might help you with that. TiS is available for Jira Server, Cloud and Data Center. Mainly, Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. It also has 4 types…
    in How can I track the instant time when a task come to a new step on my flow? Comment by Emre Toptancı [OBSS] February 2021
  • Hello @Yogesh Mude , Jira does not give this data out of the box. You either need to calculate this yourself (via custom development) or use a marketplace app for it. For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira…
    in Calculate Average days open Comment by Emre Toptancı [OBSS] February 2021
  • Hello @Thomas Harborg , As others have pointed it out, Jira does not give you this information directly. JQL can only filter issues. The search page can't show data other than issue fields. Our team at OBSS built Time in Status app for similar needs. Its date reports might help you with that. TiS is available for Jira…
    in I need to see the status of a long list of issues on a specific date back in time. with Jql. Comment by Emre Toptancı [OBSS] February 2021
  • Hello @Milan Schnorrer , The thing I am going to propose is unrelated to Harvest but I believe it can give you the same results. Our team at OBSS built Time in Status app for this need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or…
    in Harvest time tracking Comment by Emre Toptancı [OBSS] February 2021
  • Hello @Flor Mejía , A "Time Field" is a very generic description. What do you want to display in that Time Field?
    in How can I add a custom field (time in status)? Comment by Emre Toptancı [OBSS] February 2021
  • Hello @Siva Raju , Jira does not give this data out of the box. You either need to calculate this yourself (via custom development) or use a marketplace app for it. For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira…
    in How to identify issue age Comment by Emre Toptancı [OBSS] February 2021
  • Hello @Matt Davis , For an automated solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center. Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee. You can…
    in 'Average Time in Status' for Unresolved issues Comment by Emre Toptancı [OBSS] February 2021
Avatar