You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Show History of changes to Assignee - this is important to show per 9425-comment
Make configurable: allow-no-site and allow-no-assignee when creating an issue per 9425-comment
stress test i.e. push 1k, 5k, 10k, 20k, 50k issues with various number of comments and see how the feature behaves.
order card elements in main panel.
batch-close multiple issues at once.
Updates to Readme and Test Plan for the Issue Tracker module. Include design changes such as : issues must be affiliated to a specific site as of #9425, until configurable option implemented
The text was updated successfully, but these errors were encountered:
regisoc
added
GSOC
Google Summer of Code related
Proposal
PR or Issue suggesting an improvement that can be accepted, rejected or altered
labels
Oct 23, 2024
…t permission control (#9434)
- Replaced the view toggle button with a tabbed interface using `Tabs`
component
- Added permission check to show Batch Edit tab only for users with
`issue_tracker_developer` permission
- Implemented data refresh when switching back to Browse Issues tab
#### Link(s) to related issue(s)
* Resolves#9422, #9423
* Part of #9418
Follow up on #9339
After the great work introduced by @ay-bh , here are the missing points and enhancements to do:
Points for next PR, ordered by priority:
assignee/watchers changes
in comment modal.developer
permission #9422switch mode
button to another, more convenient location. Maybe close to new issue (button only appearing with the right permission).site change
in card main panel.Second priority followups
Points later on (because not part of the original ticket/issue, but still important):
developer
technical debt from [Issue tracker] make Batch mode visible only withdeveloper
permission #9422allow-no-site
andallow-no-assignee
when creating an issue per 9425-commentThe text was updated successfully, but these errors were encountered: