Time Metrics Tracker Moved to Atlassian Forge - The Story Behind the Change

[#1]

If you’ve ever tried to understand why a task gets stuck, where your workflow slows down, or how long your team actually spends in each Jira status, then you already know why Time Metrics Tracker | Time Between Statuses exists.  

                     

Teams install it for a simple reason:
they want clarity: honest, measurable, workflow-level clarity without spreadsheets, scripts, or guesswork.

And now, we’re taking the app to the next level by moving it to Atlassian Forge, Atlassian’s secure-by-design cloud platform.

This transition doesn’t just change how the app runs.
It changes how confidently you can trust the data you rely on to improve your work.

Let’s dive into the story.

What Time Metrics Tracker Actually Does

Teams use Time Metrics Tracker to answer questions that Jira doesn’t answer out of the box:

• How long do issues stay “In Progress”?

• What statuses slow us down the most?

• What’s our real Cycle Time, not just the resolution date?

• How long a task spends waiting, blocked, or reopened?

• Where exactly can we gain efficiency?

                         

In other words:
it tracks the truth of your workflow.

For engineering teams, that truth means bottleneck detection.
For product teams — predictable delivery.
For support teams — meeting SLAs.
For enterprise PMOs — visibility across thousands of issues.

And Time Metrics Tracker gives you all of it in:

• Clear time-in-status reports

• Average time charts

• Pie charts for quick insights

• Custom metric configuration

• Time range filtering

• And workflow analytics without setup

No learning curve.
No scripts.
Just the real timing behind your Jira statuses.

The Big Question: Why Move to Atlassian Forge Now?

                               

Because the industry and especially enterprise security teams is moving toward zero-trust, platform-native apps.

Over the last two years, we’ve heard the same things from large organizations:

“We want our Jira apps to live inside Atlassian’s infrastructure.”
“No external tokens.”
“No third-party hosting.”
"Full transparency and compliance."

Forge is Atlassian’s answer to that.
And we support it 100%.

Forge gives your team:

✔ Security embedded into the Atlassian Cloud
✔ Isolation of customer data
✔ Encrypted-at-rest and in-transit communication
✔ Zero token exposure
✔ Built-in compliance controls
✔ Monitoring and resilience at the platform level

When your security team sees that your reporting app runs inside Atlassian’s own cloud, it instantly solves dozens of internal checkboxes.

So our decision became obvious:
Time Metrics Tracker belongs on Forge.

The Most Important Part: Your Metrics Stay Exactly the Same

                             

We want to make one thing very clear:

⭐ None of your data, metrics, or configurations will disappear.

Everything you’ve set up stays:

• Custom Time Metrics

• Saved reports

• Work calendars

• Timezones

• Project configurations

All your logic remains — unchanged.

The migration affects the infrastructure, not your analytics.

And yes:

⭐ There will be no visual redesign.

No new UI you need to learn.
No changed navigation.
No additional setup.

Just the same interface you're used to — running on a more secure and modern foundation.

Why Teams Track Time Between Statuses in the First Place

Time Metrics Tracker exists because Jira workflows tell a story, but they don’t reveal their timing.

Two teams may have the same workflow, but completely different outcomes:

• One team moves tasks daily

• Another moves tasks weekly

• One team’s review stage lasts 2 hours

• Another’s lasts 7 days

Timing is the difference between “We’re fine” and “We’re late.”

By tracking time between statuses, teams can finally see:

Where delays happen

Is it QA? Design? Review? Awaiting customer response?

How long something was waiting

The silent killer of throughput.

How predictable your delivery is

Cycle time trends don’t lie.

Where process improvements matter most

Data makes the conversation objective.

How workflow changes affect performance

You can compare before/after.

This is why more than 500 teams choose Time Metrics Tracker.
Because visibility drives improvement and improvement drives delivery.

The Migration: What Happens Under the Hood

To move reliably to Forge, we use our secure migration service:

https://tbs.saasjet.com
(temporarily, only for configuration transfer)

It transfers:

• All your existing setups

• Working calendars

• Time metric definitions

• Page access rules

• Saved logic

Once migration is complete, this service is no longer needed.

After that, your entire Time Metrics Tracker runs on Atlassian’s infrastructure, not ours, not anyone else's.

Why You Might See https://*.atlassian.net

This is simply Jira loading its own assets:
avatars, project icons, issue type icons.

No data is sent.
No third party is involved.
It’s just Jira being Jira.

For Security Teams

                           

Security teams in enterprise environments typically look for:

• Data residency clarity

• No external APIs

• No IP ambiguity

• Vendor isolation

• Least-privilege scopes

• Encrypted communication

• No custom tokens

• Platform-native execution

Forge satisfies all of these out of the box.

This is why enterprise teams relax when they hear:

“Time Metrics Tracker runs on Atlassian Forge.”

It’s a different level of trust.
And we’re proud to meet that level.

What Improves for You After the Upgrade

1. Platform-native security (Atlassian-level protection)

Everything runs in a fully isolated environment.

2. Faster processing

Average Time and Time-in-Status calculations load noticeably faster.

3. No manual configuration

No tokens, no external setup — zero friction.

4. Reliable infrastructure

Atlassian maintains the foundation so everything is more stable.

5. Future-proof architecture

Forge is where Atlassian is heading.
Your reporting will always be compatible.

So… What Should You Expect as a User?

                   

✔ Same interface
✔ Same Time Metrics
✔ Same reporting
✔ Same filters
✔ Same workflow analytics
✔ Faster load times
✔ Higher security
✔ Placed fully inside Atlassian cloud

In short:

**Everything stays the same — except reliability.

That gets better.**

Final Thoughts — The Future of Timing Analytics in Jira

Time Metrics Tracker was built with one simple belief:

Teams deserve to understand the real timing behind their work.

With this move to Forge, that vision becomes stronger, safer, and more aligned with Atlassian’s future.

If your team cares about:

• Delivery predictability

• Bottlenecks

• SLA performance

• Capacity planning

• Process improvement

• Workflow transparency

…then timing is your most valuable metric and Time Metrics Tracker is built to reveal it.

The migration is more than a technical update.
It’s a commitment:
to security, to clarity, and to helping your team work better with every status change.

If you haven’t tried it yet now is the perfect time to install a trial and see how much timing data was hiding in your workflow all along.

👉 Try Time Metrics Tracker | Time Between Statuses on the Atlassian Marketplace