Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-60154

Filter subscription should take the column disposition defined on 'Filters'

    • 0
    • 14
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Currently, if users subscribe to a filter, they'll receive the notifications defined on 'My Defaults'. However, if this is not defined, instead of taking the disposition defined on 'Filters', it takes directly the column disposition defined for 'System'

            [JRACLOUD-60154] Filter subscription should take the column disposition defined on 'Filters'

            This would make the most sense over each user having to customize the filter.

            Alex Piwowar added a comment - This would make the most sense over each user having to customize the filter.

            The reporting capabilities of JIRA could be greatly improved with a solution that would allow for the following behavior:

            1. Filter subscriptions are rendered with unique column selection and column ordering
            2. A user could specify which columns are displayed in specific filters and then configure this specific column arrangement to be applied to specific group subscriptions to that filter.
            3. This configuration should be unique to the specific filter and not affect future or other filters (unless a default column arrangement checkbox is selected or something like that)
            4. If the default was selected containing a custom field and the custom field for a column was not available to another project, filters in those projects would exclude the columns from rendering.
            5. The subscription group member could not override the group subscription column ordering for this particular non-personal subscription unless they were the owner or delegate.
            6. A user would need to create a personal subscription to the filter in order to have a column selection or ordering that differed from the group subscription. This specific user's column ordering would only affect their personal subscription.
            7. These column selections and orderings would be used whether the filter report was rendered in a browser or composed in an automated email subscription.

            Matthew Harkins added a comment - The reporting capabilities of JIRA could be greatly improved with a solution that would allow for the following behavior: Filter subscriptions are rendered with unique column selection and column ordering A user could specify which columns are displayed in specific filters and then configure this specific column arrangement to be applied to specific group subscriptions to that filter. This configuration should be unique to the specific filter and not affect future or other filters (unless a default column arrangement checkbox is selected or something like that) If the default was selected containing a custom field and the custom field for a column was not available to another project, filters in those projects would exclude the columns from rendering. The subscription group member could not override the group subscription column ordering for this particular non-personal subscription unless they were the owner or delegate. A user would need to create a personal subscription to the filter in order to have a column selection or ordering that differed from the group subscription. This specific user's column ordering would only affect their personal subscription. These column selections and orderings would be used whether the filter report was rendered in a browser or composed in an automated email subscription.

              Unassigned Unassigned
              rrosa@atlassian.com Rodrigo Rosa
              Votes:
              24 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: