Collapse / Rollup Audits
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
Research direction
No files or tests are named. Start by tracing where audits and versions are created and how audit data is persisted to Author Bus; then clarify the version boundary and unchanged-user rules. Done means redundant audits are brought forward without collapsing audits after the last known version, reducing user-visible noise and duplicate persistence.
Written by the indexing model from the issue text.
Description
Initially we collapsed versions where if you made a version and there were no changes, you wouldn't get a new version. I think we need to do something similar (but different) for audits.
Criteria of acceptance
If da-admin feels like an audit is needed & the users have not changed, the existing audit is "brought forward".
Below you can see an example where I've been editing a doc, and there are a ton of audits, but audits 2-14 don't provide me much value.
There's probably some nuance and details to sort out on to this: if you run into a version as the last known change, we don't collapse audits that are after that version.
I'm open to other ideas. The two goals I'm after:
- Cut down audit noise to the user.
- Cut down how much we're persisting to Author Bus for what is effectively the exact same data.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from adobe/da-admin
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
saadeghi/daisyui#4780 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
accessibility bug embed websites
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quarto-dev/quarto-cli#14972 ·
Maintainers usually reply within 1 day
-
has-readme needs-attention new-tool repo-verified
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
shanselman/TinyToolTown#834 · 2 comments ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
siderolabs/talos-design-system#16 ·
Maintainers usually reply within 1 day