prometheus / prometheus/alertmanager
Alertmanger change assignee in Jira
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
hi,
early we use jiralert, it changes only some existing Issue attributes... like summary, descriptiion, priority.
But native alertmanager jira integration changes all. It cloud be not bad, but alertmanager changes field like asignee, we set it with custom fields config:
fields:
assignee:
name: super-team
I think it would be better don't change any custom fields in existing issue.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading Alertmanager's native Jira integration and the existing-issue update path, focusing on how the fields.assignee configuration is applied. Confirm which attributes are updated for existing issues and define completion as preserving custom Jira fields while retaining the intended summary, description, and priority updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100