Any progress on the item?

I am surprised I have to delete and re-add a link. It gets more tedious when I have to type/paste in the whole name too. It feels very backwards compared to other nice aspects of Jira.

It'd be nice if, like elsewhere and the modern expectation: it should be able to auto-grab the page title from a link, at least. Having some kind of visual preview with the page's favicon or an image from the page, as Notion can do for Jira issues, would be even better.

It is ridiculous that this issue was first raised in 2015 but is still an issue! There's even a later ticket (from 2016) for the same thing: JRACLOUD-41690. 

It's so frustrating that when there's a typo or there's an expected format for the text to a particular type of link for our process that has not been used or was used incorrectly that you have to create a new web link and then delete the original. (And heaven forbid that you've made a different typo the second time around because now you have to go through the whole process again.)

It's such low-hanging fruit y'all! How much time could it really take to insert an edit icon next to the delete icon and have that display the text and URL in the same format as when a web link is initially created?  

I would like this too please.

Thanks for the feedback and glad to hear that Atlassian is working on the UI aspects for a simpler user experience. As a new user coming over from Track, Mantis, Asana, and PivotalTracker, I love JIRA and see the power in it, but of all of those, it is definitely the most complex in terms of different ways to do similar tasks. It is so overly complex, I couldn't recommend it for any team that doesn't need all of its power. As general feedback to you guys, I'd suggest that you focus on consistency in how users enter or set data so that when a user knows how to do 1 thing, they know how to do everything similar. Strive to identify similarities where possible so that you achieve this, reducing the number of different steps users must learn down to the minimum.

The 3 separate edit views for an issue, each with different fields editable and a different view, is a great example of over-complexification. Continuing with this one problem with the issue screens is the tabs and "Add Tab" button for setting them up on the Configure Screen page. I saw those and thought, "Cool, I can use those to group fields for our users. I'll put the most common fields on the first tab, and relegate other fields that not everyone will need to other tabs." But then it turns out that the tabs don't even appear anywhere else! Why are there tabs there in the admin section, but not on the view in the Issue editor available to non-admin users? It appears the tabs serve no purpose but to help the administrator adding fields to organize them a bit for editing. Unless I'm missing something, this is just silly – you have added a feature for the admin (every new feature adds some complexity, which might be OK if it's also adding a function users need), but denied it from the users, which creates confusion for the admin who set it up (did I do it wrong? are tabs only visible in the admin view?). Since the tabs don't actually appear anywhere else (or if they do, how to activate this is not clear), don't even offer this as an option.

The tab issue is not to suggest a specific tab function, but rather to highlight that there is sort of another completely separate view for working with issue screens in addition to 3 I noted earlier – this oddball tab view only usable by admins in the admin section.

The whole UI is fraught with these kinds of weird inconsistencies.

Hi colin.higbie,

Thanks for your feedback. I can't say there are any immediate plans to work on this particular request. You're absolutely right that there are many areas for improvement in JIRA's UX – we need to focus our efforts on the more commonly used features.

The JIRA Agile team does intend to address the inconsistencies with editing fields in the Issue Details panel in the near future. We're definitely aware of the pain new users go through with JIRA's UI. It's our number one priority as a dev team, probably at the expense of some additional improvements those experienced users want

Thanks,
Dave Meyer
Product Manager, JIRA Platform

Luciano Fagundes created the issue for me here (thanks!). I'd like to clarify that the real issue is one of a fragmented and therefore confusing user experience, so it's probably not limited to just the Web link issue. It seems to me that when opening the Edit Issue screen (pressing 'E'), I should have access to all the fields associated with that issue. Instead, we get MOST of them, with some fields accessible only through some other weird and utterly counter-intuitive places. Web links is one such – need to close the issue, then select More | Link or clink on the Add Link button on the Agile page. Worse, we can edit JIRA task links on the issue Edit page, just not Web links.

This is related to the problem that in JIRA Agile, you have basically have a 3rd Issue screen (Issue Details), with some editable fields, but many as read-only. And that even within that, the pane width is adjustable in the Backlog view, but not in the others. This weird and inconsistent mix of UI elements is a real hindrance to picking up how to use the system by new users. I suspect it's not much of an issue to experienced users, which is possibly why you don't hear too much about these problems (most feedback tends to come from experienced users).

From a UX perspective, this is incoherent design, confusing for users, and unnecessarily complex, which probably also creates more issues for Atlassian to maintain and support. Just set up one screen that allows accessing and editing all Issue fields, especially all fields that are viewable in the standard issue views (including those that show up in JIRA Agile Issue Details).