jira

Problem Statement

Bug summary

If the first call to a jira server results in a permant redirect the next call will "forget" to include any basic auth header.

Is there an existing issue for this?

• I have searched the existing issues

Jira Instance type

Jira Server or Data Center (Self-hosted)

Jira instance version

8.13.2

jira-python version

3.0.1

Python Interpreter version

3

Is your feature request related to a problem? Please describe.

• Reduce the effort to add auto to existing projects

Describe the solution you'd like

• A preset that stays up to date with the latest auto features

mrm auto

• Document gotchas (e.g. you may have issues with an auto TS config file if your TS settings are different, make sure you have a published

Thank you for your hard work and great project!

Unfortunately we have found an issue in 1.0.

In our case, when the JiraAlert is triggered by the Alertmanager, it creates new Jira defect, without adding additional Label. For example if the service is down Jira Alert uses the label like: ALERT{alertname="ServiceDown",namespace="",service_name=""} which should already be added to Defect.

Allow editing of story point for a story in JIRA, currently it's display only

PowerMock was removed from plugin-pom due to supposed lack of activity (see #388).
Consider pros and cons of removing it from current tests.