Jira links to valid URI's don't work. Can somebody please explain how to create a link to OmniFocus

[Paul Taggart]

Hi,

Jira will not let me enter a valid URI into a Jira ticket. Can somebody please explain if this is possible please?

Thank you,

Paul

[Nic Brough -Adaptavist- · Accepted solution]

It's a non-standard uri, so it's unsupported, and not seen as a valid uri (https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml is a list of registered schemes)

Best you could do is use it plain text and install a browser extension that enables the browser to know what it means.

[Paul Taggart]

Hi, Nic.

Thank you. This is a shame as for Mac apps, a valid URI is one that has been registered with the OS.

The browser on OSX understands the URI, it's just Jira that will not let me use it.

Paul

[Paul Taggart]

Hi, @Nic Brough -Adaptavist-

For work, we're using an older version of Jira and you can create a link using any valid URI (including omnifocus:///task/bnoQ1d1J-tP) on a Mac. So the new version not allowing this is, I think, a bug as it used to work.

How can I report this issue to Jira please?

Thank you,

Paul

[Nic Brough -Adaptavist-]

Yes, later versions of Jira are a bit more sensitive on what is valid in urls and uris.  Omnifocus isn't a registered scheme, so there's no reason to recognise it as "valid" - it is correctly formed as a uri, but not an accepted standard (yet?). 

That kind of rules it out as a "bug" - the software is behaving as designed, and meets all the standards you'd care to apply.

But that doesn't mean it's good for us humans.  I think Jira should go back to doing what it did before - "if a url passes a basic check that it's valid, don't worry about the non-standard details - leave that up to the browser and/or human who clicked on it".  If we choose to put in non-standard stuff like mrflibble://says.time.to.die offer it up as a link (but maybe warn people the link isn't standard or recognise).

To ask for new stuff, use Atlassian's public tracker over at jira.atlassian.com  - that url will make you jump through some hoops because Atlassian want to encourage you to check other places (like this community) first, but to bypass all but the login, try https://jira.atlassian.com/browse.

As someone who who has spent 30 years in product support and development though, I would encourage you to try a few searches in there before raising a new one, and if you do find a good match (or related stuff), hit the vote and/or comment first!

[Paul Taggart]

Hi, @Nic Brough -Adaptavist-

Awesome, thank you.

I searched and didn't find anything of use.

I'll raise it as a request.

> it is correctly formed as a uri, but not an accepted standard (yet?).

On the mac (or an iOS device), any application can register a URI. After registration it is then considered valid. You can then interact with different apps via the URI. As an example the iOS shortcuts app uses them. The shortcuts app will be available on macOS as of the next version. I do acknowledge that this is a very 'mac centric' point of view though.

> Yes, later versions of Jira are a bit more sensitive on what is valid in urls and uris.

If I had a link out to OmniFocus on every one of my tickets at work, to allow me to easily check my todo list for that ticket, and work updated to the latest Jira these would no longer work.

Paul

[Nic Brough -Adaptavist-]

I think you're missing the point here - it doesn't matter what the client OS might be able to do, omnifocus is not a registered scheme and hence not a standard, so there's no reason for a service to support it.

Not that that matters too much for your purposes, raising the support request is the right thing to do, although I'd want to make it generic, so it can create links for any scheme, valid or not, not just omnifocus

[Paul Taggart]

Thank you @Nic Brough -Adaptavist-.

I get the point. The list of registered schemas above has been chosen for the supported list or URI's. I can also understand why, security and ensuring a consistent experience across all devices/OS's.

I'll raise a support request to request that the old style 'other' is added back in.

Paul