The changes in this PR add support for selecting tickets via an excluded-statuses setting, as opposed to a statuses setting. This makes it easier to configure and maintain workflows that use this action on projects where the desire is to move all tickets to a new sprint except for the ones that match one or more statuses.
Motivation
5
How this has been tested
I tested this on one of our project repos by adding and configuring a workflow that can be run manually. That workflow uses the excluded-statuses setting, without a statuses setting. I then moved a backlog ticket into the last sprint, ran the workflow, and confirmed that the ticket now appears in the current sprint with no other side-effects. See screenshots below.
Screenshots
Before Workflow Run
After Workflow Run
Notice ticket 2839 is in Sprint 31 and Sprint 32 shows 9 open tickets.
Ticket 2839 is in Sprint 32, which now shows 10 open tickets. Sprint 31 no longer shows up in this view, indicating there are no tickets in it.
Documentation
I updated the README and added code comments where it seemed appropriate.
agarzola
commented
7 months ago
Description
The changes in this PR add support for selecting tickets via an
excluded-statusessetting, as opposed to astatusessetting. This makes it easier to configure and maintain workflows that use this action on projects where the desire is to move all tickets to a new sprint except for the ones that match one or more statuses.Motivation
5
How this has been tested
I tested this on one of our project repos by adding and configuring a workflow that can be run manually. That workflow uses the
excluded-statusessetting, without astatusessetting. I then moved a backlog ticket into the last sprint, ran the workflow, and confirmed that the ticket now appears in the current sprint with no other side-effects. See screenshots below.Screenshots
Documentation
I updated the README and added code comments where it seemed appropriate.