🐛 Don't return issueTypes with the subtask flag set #440
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
Signed-off-by: Sam Lucidi <slucidi@redhat.com>
mansam
added a commit
to mansam/tackle2-hub
that referenced
this pull request
Jul 14, 2023
New issues that belong to issue types with the `subtask` flag set (including the "Sub-task" built in issue type) are required to have a parent issue set. We don't support setting the parent issue, so exporting migration waves as issues of such types will fail. To fix this, avoid returning issue types with the `subtask` flag set from the `/trackers/:id/projects/:pid/issuetypes` endpoint. Fixes https://issues.redhat.com/browse/MTA-870 by removing the option to export as a Sub-task. Signed-off-by: Sam Lucidi <slucidi@redhat.com>
mansam
added a commit
that referenced
this pull request
Jul 17, 2023
Backport of #440 Signed-off-by: Sam Lucidi <slucidi@redhat.com>
This was referenced Nov 22, 2023
This was referenced Jan 23, 2024
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.
New issues that belong to issue types with the
subtaskflag set (including the "Sub-task" built in issue type) are required to have a parent issue set. We don't support setting the parent issue, so exporting migration waves as issues of such types will fail. To fix this, avoid returning issue types with thesubtaskflag set from the/trackers/:id/projects/:pid/issuetypesendpoint.Fixes https://issues.redhat.com/browse/MTA-870 by removing the option to export as a Sub-task.