Cannot make universally visible permalinks to saved filters / Permalink behaviour is inconsistent

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Answered
    • 6.0
    • Component/s: None

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      1. Create a new search filter
      2. Note that the permalink to the filter is a JQL query so will return results for anyone who clicks it
      3. Save the filter
      4. Note that the permalink to the filter is no longer a JQL query, but a link to the saved filter's ID.

      Firstly, I dislike that the behaviour of the permalink button changes depending on whether your filter is a saved one or not. This is really poor user-experience, especially as it's quite easy to overlook whether you are viewing a saved filter or not.

      Secondly, once a query has been saved the permalink button becomes completely non-functional unless I also share the filter with the intended recipients first. Once I've shared the filter, there is very little need for the permalink button in the first place because the intended recipients will be able to find the filter in their list of available filters. As you can only share on a group level, it can be quite tricky to work out which groups you need to share with to get all the right recipients included. You might have to share with a lot of unnecessary people, if your intended target group is quite small.

      This has come about because of JRA-28914 with which I quite strongly disagree. In my opinion, the permalink button should be a permanent link to the current set of results that I'm looking at. Sharing filters is the way to get a dynamic set of results that updates if/when you change or save the filter.

            Assignee:
            Unassigned
            Reporter:
            Sarah Woodhouse
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: