-
Suggestion
-
Resolution: Unresolved
-
None
-
39
-
Team, the commenting experience has been refreshed as per the 8.17 release notes, and it seems the removal of the Ability to link to a specific comment "Permalink" function for comments made several of users unhappy.
Tickets may have several comments and a Permalink was an easy shortcut to an specific comments, instead of loosing time looking format comment.
We have researched in our knowledge bases and documentations to understand why this feature has been removed but no former reason was found.
It has been found the same feature issue for Jira Cloud, but it seems it has been fixed, but not yet for Jira Server / Data Center.
This is the ticket where this feature was fixed for Jira Cloud. JRACLOUD-70156
Although we have an official workaround for this Link to a comment missing after an upgrade, Customers are still asking for this feature to be back.
If we have successfully got this feature back in Jira Cloud I'm suggesting an effort to ship this feature back as soon as possible on Jira Server / Data Center as well.
Thanks for the attention.
Please advise.
- links to
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-72757] Lack of a Permalink feature in the new view in Jira 8.17 and later
2f5b443db8d5 Service project aren't in the scope of Jira Software, they're part of Jira Service Desk, a separate product.
We encountered the same issue, however the key distinction lies in the functionality across project types.
It works with Service projects, yet we don't see the icon in Software and Business projects
Of course it made several users unhappy. You had a beautifully intuitive and visible icon approach in the past. And you made that un-intuitive. Invisible. All to save only the tiniest bit of screenspace. Space that is still easily found and available on the page.
The use of relative time exacerbates this. I did get used to finding links in dates, but not in relative words like "yesterday" (a nearly useless generalization on its own when you are a software developer)
Please fix this bug - the "workaround" does not work for v9.4.7 - the page does not scroll to the proper comment.
This should be fixed especially because the recommended workaround doesn't work: if I copy the link from the timestamp and navigate to that address, the ticket opens without jumping to the comment and the URL actually redirects to the URL of the ticket without the comment ID
Why is this ticket tagged a "suggestion" and not a "bug"?
It looks a regression for us.
Having documented since when 8.17 the issue was introduced would make people upgrading (like us) aware of the issue.
permalink is a must have feature, otherwise tracking becomes much difficult . Please reinstate this feature asap.
So, details matter. This really on affected software projects. JSM projects still have the permalink. Is another workaround to go ahead and make all projects JSM whether you deploy a portal or not? 
Yes, please add a perma-link to comments. The work-around is not an obvious one (right-clicking the timestamp). Many users certainly give up once they see there's no perma-link. Thanks.