blombard / move-to-next-iteration

Automatically move issues to next iteration
MIT License
30 stars 13 forks source link

Different weekly-sprint dates in the action #7

Closed tty47 closed 6 months ago

tty47 commented 6 months ago

hello!

I'm facing issues when moving from the previous weekly sprint to the current one, it looks like the action has/detects different dates...

The first part is where the action moved the issues, and the second weekly sprint is the real current one:

Screenshot 2024-01-29 at 07 27 50

I have this config:

name: Move To Next Iteration

on:
  workflow_dispatch:
  schedule:
    # Runs "at 05:00, only on Monday" (see https://crontab.guru)
    - cron: '0 5 * * 1'

jobs:
  move-to-next-iteration:
    name: Move to next iteration
    runs-on: ubuntu-latest

    steps:
    - uses: blombard/move-to-next-iteration@master
      with:
        owner: <project>
        number: <id>
        token: ${{ secrets.PROJECT_PAT }}
        iteration-field: "Weekly-Sprint"
        iteration: last
        new-iteration: current
        excluded-statuses: "Done"

is there something wrong?

thanks in advance!

blombard commented 6 months ago

Hi @jrmanes, I think the problem here is that we are updating the iteration with its title, which of course isn't ideal, but that's the way it is.

To make it work you would need to add a differentiator in your titles. E.g. Weekly-Sprint 5 - 2024

tty47 commented 6 months ago

Hi @jrmanes, I think the problem here is that we are updating the iteration with its title, which of course isn't ideal, but that's the way it is.

To make it work you would need to add a differentiator in your titles. E.g. Weekly-Sprint 5 - 2024

hey @blombard thanks for your response, it worked! I had to update it like this:

Screenshot 2024-02-04 at 12 44 52

and the code. iteration-field: "Weekly-Sprint - 2024 -"