prometheus / prometheus/alertmanager
Custom JQL for Jira tickets
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
Hi,
First, thanks everyone who contributes to this project,
I was wondering if there are other ways to lookup/create tickets without creating ALERT{Hash} every time?, at the moment the only way of looking up for existing Jira tickets is through label, project
/notify/jira/jira.go#L222
, which leads to creating a unique label on every unique alert. Overtime, it floods Jira by labels, which may not be a way to go in some environments.
Any comments on this particular case?
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
Read notify/jira/jira.go around line 222 to understand the current label-and-project lookup and ticket creation flow. Define how custom JQL should be supplied and what lookup and creation behavior should replace the per-alert ALERT{Hash} labels; done means the requested Jira workflow is supported without flooding Jira with unique labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100