Support board quick filter
Description
We should display on shared board same filter that are available on Jira board as a configuration option.
All quick filter, some quick filter, non-quick filter.
We should add possibility to define custom quick-filters for shared board.
We want to ensure that those currently 2 default quick filters will stay for existing shares and new share will have them added by default:
Open
/ Recently updated
Linked issues
blocks
ESFJ-721
Support custom quick filter
Withdrawn
Activity
Show:
Hello @Mykhailo Iereshchenko,
Please merge code to dev branch.
This is the best moment to add more information that can be helpful to prepare release notes.
Can you prepare short overview of change that can be used in release notes?
Please provide short GIF that showcase feature.
If GIF make no sense, can you provide image that highlights feature that can be used in release notes (cropped & annotated)?
Improvement implemented - QA env
labels = "Test2" AND priority = "Lowest" AND status = "In Progress"
Hello @Mariusz Szymański,
Task is ready for review.
@Mykhailo Iereshchenko please make sure reviewer
have easy access to contend to be reviewed.
If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.
A new "Quick Filters" tab has been added to the board configuration. Users can now select which quick filters to include on their board. All existing boards will automatically have two default quick filters, "Open" and "Recently Updated," pre-added. When a new board is created, these two default filters will also be added automatically, but users have the option to remove them. Users can create their own custom quick filters, select from existing Jira board filters, or add the default quick filters. While creating custom quick filter validation for both name and jql field is present. If share is not board, “Quick filters” tab is not shown.
Hello @Mykhailo Iereshchenko
This is the best moment to add more information that can be helpful for tester.
What areas are affected?
What are potential edge cases?
Was it checked for XSS problems?
Does change affect security, is new data exposed?
Please attach - Before / After screenshot if possible.
Hello @Mykhailo Iereshchenko,
Change was reviewed and approved.
Task is ready to be deployed to QA.
Once it is deployed to QA please move ticket to "To Test"
Thank you!
@Mykhailo Iereshchenko Changes requested
Hello [~accountid:],
Task is ready for review.
@Mykhailo Iereshchenko please make sure reviewer
have easy access to contend to be reviewed.
If this is code change. Please make sure PR is created.
If this is new documentation, blogpost, etc. Please provide link to page.
1
2
3
4
5
6
7
8
9
10
11
12