-
Suggestion
-
Resolution: Unresolved
-
None
[ATLAS-137] Jira Project vs Atlassian Project (in Home) nomenclature confusion
I also asked about this here, as a part of the issue rename to work, but Jira projects seems to have been the real misnomer (long been used with a lot of muscle memory). Not sure of the best way to solve it.
Even though a ton of work for me and others, seems like they both could use a rename. Jira projects to space or workspace maybe? And Atlas projects to segment or stream or milestone or initiative or program or loop (to tie into The Loop concept, but that it really on the goal/OKR level too)?
Atlas "project" makes sense but will just continue to get confused with a Jira project (incorrect terminology, but been around forever).
Thanks for raising this issue.
It's not just Jira projects vs Atlassian Home projects, but also our internal business projects, which we have a bespoke issue type above Epic that we use to manage projects with 'project' in the title. The work within these 'projects' is managed within one or more Jira projects. In addition other parts of the business have 'projects' which are managed less formally via 'Epics' within Jira projects.
From a users' perspective, this is the comment we gave Gunjan to the way you have designed 'Goals' as a feature:
"We already feared as much unfortunately, but then, what is the use of linking 'Projects' to Goals at all when it is impossible to link the actual Projects that are the parent to the issues, epics and other tickets that 'live' in Jira, not 'Atlassian Home'?
This seems a bit useless to us, but perhaps we are missing the way Jira engineers intended the use of Goals in the first place? From our perspective: The only added value of Goals is when we can formulate goals that are linked to the highest hierarchy of work to be done, namely an entire project. There is no added value linking goals to individual (smaller) tickets/ work to be done as these are merely "to do's" in a higher Project, which do not 'live' in Atlassian Home, but in Jira, which represents the 'factory'. By being able to link Jira Projects (instead of Atlassian Home Projects, which frankly, I have no idea what they do, ideally all Epics, tickets and tasks that encompass that Project would be automatically linked and reporting would be automatically updated when anything is added or changed).
It would have been great if we could have incorporated risk assessment into our 'factory' for example, which we now do in separate documents, making it less efficient for us to remain compliant. Also, dashboarding would been improved by this feature on our 'factory' by this feature if we could have used it.
For this reason, there is no use for us for Goals and therefore, there is no solution for this query for us until you may decide to alter this feature in the future.
Thank you for clarifying for now and perhaps we may use this featurew in the near future should you decide to change it 🙂. I shall follow the request as advised.
Kind regards,
Dirk Jan Boer