Where should we report Forge bugs?

I’m trying to figure out the best place to report Forge bugs.

A lot of bug reports in the FRGE project on ecosystem.atlassian.net go unanswered and remain in the “Needs triage” status for quite a while (sometimes years). Recently, however, two of the bugs I reported (FRGE-1738 and FRGE-1800) were fixed without any updates to the tickets, which makes me wonder if they’re being tracked somewhere else.

Additionally, this comment from November last year suggests that the FRGE project will be discontinued and all bugs and feature requests will be moved to JAC:

We are no longer creating bug/suggestion requests in the FRGE project. Instead, we’re gradually moving all existing open tickets to JAC. Using JAC as our primary bug tracking system allows all our developers, partners and customers to easily find and track bugs/suggestions in one centralized location.

Does this mean that it’s better to report Forge bugs to developer support by opening ECOHELP tickets instead of creating tickets in FRGE?

3 Likes

I asked this question multiple times in the last years to multiple peoples at Atlassian, and I always get a different answer :upside_down_face:
I think they really don’t know. And yes, nobody is in charge of the FRGE board, which results in a big mess.

We nevertheless continue to report all bugs/missing features on FRGE, and then we try to find the right PM/person at Atlassian to push things forward.

3 Likes

Hi @klaussner - I’m chasing down a proper answer for you, but the short answer is that there was an internal project running to shut down the FRGE project on ecosystem.atlassian.net and migrate all bug + suggestion reporting for Forge to the ECO project on jira.atlassian.com.

The intent behind this project was to align the Forge team with the rest of Atlassian’s tooling and patterns for triage and management of issues, which all happens on jira.atlassian.com.

However, that project stalled out due to some technical difficulties and it has left us in a limbo state.

No denying that the FRGE project is a bit of a mess, but it’s still a reasonable place to have a ‘source of truth’ issue for any bugs or feedback you encounter.

I’ll see what I can do about getting an updated answer about the direction we want to head with clearer feedback channels in the future.

8 Likes

@HeyJoe any update on this?

3 Likes

Ownership of the project to consolidate our feedback channels has been impacted by the recent restructuring of Atlassian’s support organisation - I’ve set myself a goal of getting some clarity here by the end of the year.

In the meantime, reporting issues in the ECO project is preferable, if you can, otherwise use the FRGE project.

4 Likes