One aspect I haven’t seen covered here or in any of the ACJIRA issues is how Jira project page URLs should be constructed once user.id and user.key are removed by AC-2417.
Our app has a project admin panel, and when you click on it in the Jira navigation it takes us to a path like this that contains user data:
/plugins/servlet/ac/com.thinktilt.proforma.add-on/project-forms?user.key=admin&project.key=SERVICE&project.id=11215&servicedesk.serviceDeskId=35&user.id=admin
The question is what is going to happen to that URL after the migration period? If Jira simply drops the user data from the URL then navigation is likely to break. That’s what happens if we do that now… if we manually change the URL to this:
/plugins/servlet/ac/com.thinktilt.proforma.add-on/project-forms?project.key=SERVICE&project.id=11215&servicedesk.serviceDeskId=35
Then our page displays but the navigation is broken:
This is a problem for us because we have internal navigation between parts of our app — we have links from other pages to this project page. We will have to remove the user key from the links we generate, but if we do that now the navigation will be broken so we don’t want to do it yet!
Ideally Jira could give us the links so we don’t have to generate them ourselves and deal with the user problem. However the AP.navigator.go API which should do that is currently broken so we can’t use that either (we raised ACJIRA-1678 on that a few weeks ago).
So my question is what links should we be using for project pages? And will the navigation bar keep working after the GDPR migration removes user data from URLs, or is that a bug which hasn’t been dealt with yet?