-
Suggestion
-
Resolution: Unresolved
-
None
The new Navigation Change in Jira is substantially different and requires multiple pages of training when this may already be available via in-product onboarding.
However-- as indicated by this article, it's not supported for On-Premise instances
https://community.atlassian.com/t5/Jira-Align-articles/A-new-navigation-experience-is-coming-to-Jira-Align/ba-p/2412314
Will there be any differences between Cloud and on-premise instances?
Because the in-product guides are built with Pendo, on-premise customers will not receive in-product onboarding. We recommend using the above video and our Help Center articles to get started. Additionally, on-premise customers will not receive in-product feedback requests about the new navigation.
The request is to understand what needs to be done to enable In-App navigation by 10.128.2 or 10.129.2
IMPACT
This would impact any large on-premise customer (we are likely the largest) Align has AND improve the experience for migration to the NewNavigation after 10.127.x
WHY
Atlassian currently disables all Pendo Analytics and Onboarding for On-Premise customers as indicated https://community.atlassian.com/t5/Jira-Align-articles/A-new-navigation-experience-is-coming-to-Jira-Align/ba-p/2412314
WHAT
ENABLE in-app onboarding via feature flag
- resolves
-
ALIGNSP-21903 You do not have permission to view this issue
-
[JIRAALIGN-6181] On-Premise support for In-product Onboarding
- Today: Atlassian likely has a setting that disables this logic for all OP instances something like “IF (ONPREMISE) then disable Pendo Analytics and 3rd party guides” – this is a reasonable since some firms do not want any data sent out.. this is understandable but this shoud be an option to enable
- Recommendation: Enable “ALLOW” pendo analytics and 3rd party guides via feature flag code
-
- This is relatively easy to do since would use the existing feature flag functionality that already exists in the system. This also allows OP to choose to enable to disable this functionality and is off by default to ensure other OP customers are not impacted
-
- From what we can tell – this functionality is just disabled so it is likely a minor change in the code to enable this via feature flag if there is already a flag or configuration to disable or enable this functionality
- Impact: It helps resolve multiple issues in regard to migration from Old NAV to New NAV for ALL customer and users
Dropping this request since there is limited on-boarding screens. Atlassian is not investing in this.