Birkan Yildiz _OBSS_

Hi @Abhishek P, Identifying bottlenecks before they impact delivery timelines comes down to moving from reactive reporting to proactive workflow monitoring. Standard Jira board views show what is currently assigned, but they don't easily highlight where work is silently sitting still. Here is how high-performing teams…

in How do you identify bottlenecks in Jira before they start delaying project delivery? Comment by Birkan Yildiz _OBSS_ November 4

Hey @Mohit Verma, Exporting JSM tickets along with custom fields, comments, and worklog details for internal audits is a very common requirement, but it comes with a few native caveats in Jira. If you need an out-of-the-box audit report that neatly structures field values, comments, and changes into exportable Excel…

in I need the data exported in excel for tickets Comment by Birkan Yildiz _OBSS_ October 28

Hi @Kyle Zuo, Reconciling contractual SLA-based credits in Jira Service Management can be tricky because JSM natively tracks individual SLA timers (Met vs. Breached per ticket), but it doesn't map those results to contractual billing periods, target SLA success-rate thresholds, or invoice credit calculations. In practice,…

in How do JSM teams reconcile SLA-based invoice credits for external customers? Comment by Birkan Yildiz _OBSS_ October 22

Hi @Masa, Preparing separate monthly reports manually for 20, 50, or 100+ customer organizations in Jira Service Management is a common challenge that takes up a massive amount of time when relying on native Jira features or manual spreadsheet exports. If you are open to using an Atlassian Marketplace app, TicketBook -…

in How do you handle monthly customer reporting across multiple JSM organizations? Comment by Birkan Yildiz _OBSS_ October 22

Hey there, welcome to the Community! To answer your JQL question first: status = "Waiting for Customer" AND NOT status CHANGED AFTER -3d will find issues whose status hasn't changed in the last 3 days. However, if you use this directly in a daily scheduled Jira Automation rule without tracking labels, it will keep…

in Send Reminder Email to Reporter When Ticket in Waiting for Customer from Past 3 Days Comment by Birkan Yildiz _OBSS_ October 22

Hey @Tomas Greif, Hey there, welcome to the Community! Sorting by Jira's native Updated timestamp often causes this exact problem, as minor edits like updating labels or fields bump the issue to the top even if it was completed months ago. If you are open to using a Marketplace app, you can easily get the exact transition…

in Get Done ideas by the the date when it was moved to Done Comment by Birkan Yildiz _OBSS_ October 22

Hey there, First of all, welcome to the Atlassian Community! If you have access to developer tools, you can extract the full changelog programmatically using the Jira REST API: Call /rest/api/3/issue/{issueKey}?expand=changelog for each ticket in your filter. Parse the changelog.histories array to look for items where…

in Sprint change for Issue ticket report Comment by Birkan Yildiz _OBSS_ October 6

Hey there, To answer your question directly: Yes, it is possible to retrieve the original value, provided the field was modified or overwritten at any point after creation. Here is how Jira records this data and how you can recover those lost values: How Jira Stores Creation Values Natively, Jira does not maintain a…

in How to Retrieve the Original Value Entered in a Custom Field During Issue Creation Comment by Birkan Yildiz _OBSS_ October 6

Hey, Since you’re using Jira Server, Field Sync by OBSS might be exactly what yo u’re looking for. Field Sync automatically keeps field values synchronized between related Jira issues. You can create listeners for parent ↔ sub-task, Epic ↔ Story, linked issues across projects, and Advanced Roadmaps/Portfolio parent ↔ child…

in Bidirectional Issue Syncing Across Projects Comment by Birkan Yildiz _OBSS_ October 5

Hi, Implementing Flow Metrics like Flow Time / Cycle Time, Lead Time, Flow Load, and Flow Efficiency) natively in Jira can be challenging because native Jira operates on a continuous 24/7 clock and doesn't easily calculate elapsed durations between workflow states or store them on individual work items. To successfully…

in how to implement flow metrics implementation and reporting in atlassian Comment by Birkan Yildiz _OBSS_ October 5

Hey Karl, Custom field-based elapsed time calculators often return 'None' due to field re-indexing issues, field context/screen mismatches, or limitations in how Jira logs custom field timestamps during sub-task workflow transitions. Setting up and maintaining custom fields for status durations, especially for sub-tasks,…

in JEP not measuring elapsed time duration between status. Comment by Birkan Yildiz _OBSS_ October 1

Hey Akankshya, As a Scrum Master, the best dashboard metrics are actionable flow indicators that trigger immediate conversation or process adjustments during sprint planning and retrospectives. Vanity metrics look nice, but flow metrics reveal the truth. If I had to choose 5 actionable metrics for a Scrum Master dashboard,…

in I want to know as a scrum master which Jira metrics do you actually use to understand sprint health? Comment by Birkan Yildiz _OBSS_ September 30

Hey Lucas, If you want a simple, reliable way to handle this without creating custom timestamp fields or managing complex multi-rule automations, you can use Timepiece - Time in Status for Jira. Here is how easily Timepiece solves this: True Uninterrupted Tracking: Timepiece reads Jira's issue history log directly,…

in Jira automation Waiting for customer Comment by Birkan Yildiz _OBSS_ September 30

Hey Priya, Writing a custom Python script to fetch Jira changelogs, calculate SLA metrics, and send out weekly emails is certainly possible via Jira's REST API. But, IMHO, building and maintaining that parsing logic can quickly become a complex project. If you are open to using a Marketplace app to save that setup time,…

in Automate sending emails using python Comment by Birkan Yildiz _OBSS_ September 30

Hey @Nugzari Turashvili Relying solely on averages can be highly misleading because they mask the real story of your team's performance. A single outlier ticket that was blocked or waiting on a customer for weeks can skew your average upward, making it look like your team is slow when in reality they resolved every other…

in which report is a accurate for time to resolution Comment by Birkan Yildiz _OBSS_ August 20

Thanks for the contribution @Mia Tamm _Simpleasyty_ BR

in Jira Audit Log vs. Issue History: What Each Tracks, and How to Report Across Work Items Comment by Birkan Yildiz _OBSS_ August 18

Hey @Svetlana Mandrosova , First of all, welcome to the Atlassian Community! If you are open to using a marketplace app, you can easily build this report using Historian - Issue History for Jira: JQL Scope: Run a JQL query in the app to find your target issues (e.g., project = MYPROJECT AND status WAS "In Testing"). Select…

in How to report on the assignee of a Jira story while it was in "In Testing" status, using history Comment by Birkan Yildiz _OBSS_ August 17

Hey @Mia Tamm _Simpleasyty_ As you pointed out, by shifting the focus to extracting these metrics directly from the transition history, we keep the instance clean, scalable, and performant. And still giving teams the flexibility to ask any time-based question they want about that underlying journey. I’m really glad that…

in Time Between Statuses: Explained Comment by Birkan Yildiz _OBSS_ August 13

Thanks, @Anwesha Pan . Glad you found it useful.

in 4 Ways Agile Teams Reuse One Time in Status Report Comment by Birkan Yildiz _OBSS_ August 12

Very informative. thanks.

in Jira Time in Status: What It Is, How to Track It, and Native vs. App Comparisons Comment by Birkan Yildiz _OBSS_ July 30

Hi @jack_verstappen First, welcome to the Community! Managing entitlements and tracking requests across multiple customer and partner organizations can be quite complex to report on using native Jira Service Management features alone. If you are open to using a Marketplace app, using a contract management app makes this…

in How to deal with an external partner organisation that works with multiple customer organisations Comment by Birkan Yildiz _OBSS_ July 27

Hey @piyushgupta , Native Jira dashboards and gadgets offer great basic reporting, but they do not natively support advanced, multi-dimensional KPI tracking like daily/weekly trends grouped by custom fields (Region, Team) alongside exact ticket aging or reopen counts. If you are open to using a Marketplace app, you can…

in Dashboard Comment by Birkan Yildiz _OBSS_ July 21

Hey @slucchesini As Alexandre mentioned, there is indeed a magical "Field value duration" add-on, so you do not need to change your flexible architecture or build heavy API scripts to parse issue histories! You can easily track these exact metrics using Timepiece - Time in Status for Jira. Here is how you can get your team…

in Field value duration for BI purpose Comment by Birkan Yildiz _OBSS_ July 21

Hey @Emma Handley First, welcome to the Community! This is Birkan from the Timepiece - Time in Status for Jira team. To answer your question directly: Yes, Timepiece - Time in Status for Jira provides exactly this functionality for both Jira Cloud and Jira Service Management. Here is a more detailed guide on how you can…

in How I can obtain the status of Jira tickets at a specified date? Comment by Birkan Yildiz _OBSS_ July 20

Hey @Kristy, Native Jira burndown charts and sprint-based gadgets won't work well for your Kanban setup since they rely heavily on active sprints. If you are open to using a Marketplace app, you can build this exact view using Timepiece - Time in Status for Jira. Here is how you can set up a time trend gadget for your…

in time gadget for non-sprint time analysis? Comment by Birkan Yildiz _OBSS_ July 16

Hey @Williams_ Dave First, welcome to the Community! While native Jira records the "Created" and "Resolved" dates, it doesn't natively provide a built-in "duration" field that easily calculates the exact elapsed time a ticket was open without relying on complex JQL or workarounds. If you are open to using a Marketplace…

in How do I track the duration of a ticket Comment by Birkan Yildiz _OBSS_ July 16

Hey @Singh_ Rahul_ENG_ First, welcome to Community! Native Jira search is flat, and there is no built-in way to expand linked issues in the same view. Manually checking hundreds of stories for traceability matrices takes way too much time. If you are open to using a Marketplace app, you can get this exact view using…

in Support "Stacked" / Linked Issue Expansion in JQL Results Comment by Birkan Yildiz _OBSS_ July 15

Hey @Fabricio Riveros Native Jira does not offer a built-in way to report on a "Carryover Count" per issue. While you could try building a Jira Automation rule, it is fragile, requires constant maintenance, and will not work retroactively for your completed sprint history. If you are open to using a Marketplace app, you…

in How to track sprint carryover count per issue in Jira Cloud? Comment by Birkan Yildiz _OBSS_ July 8

Hey @teh_kt This is Birkan from the Timepiece – Time in Status for Jira team. To track Cycle Time with Timepiece, please check out this step-by-step guide. If you'd like, we're also happy to schedule a free online demo. Feel free to reach out anytime; we'd be glad to answer any questions you have about Timepiece and track…

in Timepiece App to measure monthly metrics Comment by Birkan Yildiz _OBSS_ July 1

Hey @Debbie Crum First, welcome to the Community! Yes, native Jira calculates the total resolution time continuously from creation to closure, including all the time a ticket spends waiting on requestors or third parties. It doesn't natively allow you to "pause" the timer for specific waiting statuses. If you are open to…

in Tracking Question Comment by Birkan Yildiz _OBSS_ June 24

Birkan Yildiz _OBSS_ Atlassian Partner

Comments