Remove plugin.overwriteIssueSummary option
#123
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17 tasks
csvtuda
changed the title
plugin.overwriteIssueSummaries optionplugin.overwriteIssueSummary option
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the wake of #114, this PR removes the
plugin.overwriteIssueSummaryoption. From now on, issue summaries are automatically fetched for all linked test issues, preventing undesired behaviour as described in #100 or #83.The only summary which users can now still change is the summary of linked test execution issues, through the
jira.testExecutionIssueSummaryoption.Any issues updated after a Cucumber feature file import are also renamed to their previous summary on upload. Effectively, Jira is now the only source of truth for issue summaries.