AFAIK, filter IDs are currently auto generated with the ID falling in the [0-9]* range. It would be supercool if the ID could carry some custom semantics, using at least [a-z0-9-]*
The form for this could look like this:
and the result could be e.g.
https://jira.example.com/issues/?filter=rn-123
Is this doable?
I'll quickly elaborate the example which will hopefully show that such a feature added to the filter ID could be useful.
it is clear to me that it is mainly the filter's name which should be the main carrier of the filter's meaning. However, there are many times and many occasions when you want to send out just a link, without the full name of the filter.
Now if you had the suggested (limited) semantics in the filter ID itself, it would be a super improvement for such situations: the receiver of such a message (just the filter ID) - whom I expect to find oneself in the context of the message not for the first time - would instantly now what the filter is about.
Thus, seeing
https://jira.example.com/issues/?filter=rn-4-7
I'd infer: This JIRA filter is for all tickets related to Release Notes 4.7.
instead of receiving just
https://jira.example.com/issues/?filter=1687951
in an email message.
To make that useful, you'd have to embed meaningful information in the data and impose complex rules on the naming conventions.
It's unneccessarily complex and pretty much pointless. It would be far easier and more useful to implement a scheme that allows you to refer to filters by name as well as ID in the url (There's a request for that somewhere in the backlog)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not without rewriting the code that handles the generation of IDs (it's a simple increment on the last number in the database), and all the code that expects to retrieve filters by their id
I'm not sure that it is particularly useful change - the id is a background thing, the filter name is there to be indicative of what it's for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.