Configurable available notification data
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
The issue does not name files or tests. First locate the notification table, how it gets device data, and where user preferences are configured. Done means users can choose which available device data appears in notifications, without adding every data point as a default column.
Written by the indexing model from the issue text.
Description
Is there an existing issue for this?
- I have searched the existing open and closed issues
Is your feature request related to a problem? Please describe
The notification table currently exposes a fixed set of device information. As more integrations provide additional metadata, the table can become increasingly crowded with fields that may only be useful to some users.
Describe the solution you'd like
Instead of adding every available data point as a default column, provide a configurable way for users to choose which available device data should be included in notifications.
Describe alternatives you've considered
n/a
Anything else?
n/a
Am I willing to test this? 🧪
- I will do my best to test this feature on the
netlertx-devimage when requested within 48h and report bugs to help deliver a great user experience for everyone and not to break existing installations.
Can I help implement this? 👩💻👨💻
- Yes
- No
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 456
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 30
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a 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 netalertx/NetAlertX
-
Docker 🐋
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug 🐛 Contributors 🙏 help wanted 🆘
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug 🐛 next release/in dev image 🚀 Waiting for reply⏳
Difficulty 3/5 Half a day Newbie friendliness 57/100
netalertx/NetAlertX#1852 · 1 comment ·
Maintainers usually reply within 1 day
-
bug 🐛 next release/in dev image 🚀 Waiting for reply⏳
Difficulty 4/5 3-5 days Newbie friendliness 48/100
netalertx/NetAlertX#1831 · 2 comments ·
Maintainers usually reply within 1 day
-
Feature request ➕ please feedback 💬
Difficulty 5/5 Over a week Newbie friendliness 45/100
netalertx/NetAlertX#1827 · 1 comment ·
Maintainers usually reply within 1 day
All issues in netalertx/NetAlertX
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fossasia/visdom-dev#77 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aws-cloudformation/cfn-lint#4890 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
volcengine/OpenViking#6521 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
AstrBotDevs/AstrBot#10720 ·
Maintainers usually reply within 1 day