⚠️ Potential Issues with Flow Time Assessment

Stay aware. Stay accurate.

🔄 Jira Workflow Quirks

Flow Time Report relies on Jira changelogs. Some edge cases may affect the precision of the timeline:

🧱 1. Missing Status History

If an issue was created but never transitioned (e.g., still in "To Do"), Jira changelog may not include any status history.
🟢 What we do: We assume the issue entered its current status at created.

🌀 2. Repeating Statuses

Returning to a previous status (e.g., "In Progress" ➝ "In Review" ➝ "In Progress") creates multiple entries in the timeline.
✅ This is by design — each visit is treated independently and timed separately.

🧍‍♂️ 3. Unknown User or System Updates

In some automated transitions (e.g., via workflows, integrations), the user field may be missing.
👻 We show "Unknown User" if author.displayName is not present.

🕳 4. Status Not Set in Time

Sometimes Jira APIs delay updating status. If timestamps overlap or come back null:

• Duration will be 0m (we avoid negative durations).

• The issue might not appear in the table — rare, but possible.

🕐 5. Clock Drift / Timezones

Flow Time Report uses ISO timestamps from Jira API, assuming the server is timezone-consistent.
🕒 Time displayed follows your Jira timezone settings — not system time.

🛡️ 6. Permissions Limitations

If your app permissions are too restricted:

• issue.property for badges won’t be saved

• changelog won’t be accessible

• You’ll see an error or empty table

👉 Make sure the app has access to READ changelog and WRITE properties.

🧰 Recommendations

✔ Don’t rely on changelog for legal/time billing accuracy
✔ Use it as an operational insight tool
✔ Always double-check transitions in Jira when in doubt