github: update of .jira_sync_config.yaml#304
Merged
Merged
Conversation
…l for the synchronization with Jira Signed-off-by: Maria Seralessandri <maria.seralessandri@canonical.com>
roosterfish
reviewed
Dec 18, 2024
roosterfish
approved these changes
Dec 18, 2024
Contributor
|
@mseralessandri can all of those bug sync epics be linked under a central epic (or another type) so they can be found easily in Jira? Just an idea. |
Contributor
Author
You can link the epics only to objectives but then they would appear in the road map |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I changed the 'jira_key' and 'components' in .jira_sync_config.yaml configuration file for the synchronization with Jira.
The issues in MicroCluster will be created in a separated epic and the 'component' key will allow filtering by 'MicroCluster' key