Make Jira templates more configurable and safer #124
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
|
@zhanglu1122 Can you help review this? |
|
@qgong Thanks for your review. I've added another change (see the latest commit) to drop setting the |
hluk
force-pushed
the
jira-templates
branch
4 times, most recently
from
991058d to
f20600e
Compare
Enables configuring Jira fields and labels using a config file. Path to the config file is set by `RETASC_CONFIG` environment variable. This uses mapping for field names in template files to Jira issue properties, because the property naming in Jira are often inconsistent (as in camelCase, snake_case). This also ensures that the template files only use known Jira properties, labels contain internal ID labels and field for release name cannot be overridden. Uses only labels to identify issues for given release. URLs and paths for rules and template are also taken from the config files. CLI command `generate-schema` generates schema for the config file. JIRA: RHELWF-10977
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.
Enables configuring Jira fields and labels using a config file. Path to
the config file is set by
RETASC_CONFIGenvironment variable.This uses mapping for field names in template files to Jira issue
properties, because the property naming in Jira are often inconsistent
(as in camelCase, snake_case).
This also ensures that the template files only use known Jira
properties, labels contain internal ID labels and field for release name
cannot be overridden.
Uses only labels to identify issues for given release.
URLs and paths for rules and template are also taken from the config
files.
CLI command
generate-schemagenerates schema for the config file.JIRA: RHELWF-10977