Assinged issue did not move "Project already has the associated issue"
See original GitHub issuehi there!
I have one project with three column and one issue on the Todo column. i want to move the issue when i assign it to some one.
my workflow:
on:
issues:
types: [assigned]
jobs:
automate-project-columns:
runs-on: ubuntu-latest
steps:
- uses: alex-page/github-project-automation-plus@v0.1.3
with:
project: presentaion project
column: In progress
repo-token: ${{ secrets.GH_PAT }}
but i’m keep getting this error:
with:
project: presentaion project
column: In progress
repo-token: ***
##[error]Project already has the associated issue
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Moving assigned issues on project boards - GitHub Docs
Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is...
Read more >Moving an issue | Jira Service Management Data Center and ...
You must have the Move Issues permission for the project that has the issue that you want to move. You must have the...
Read more >Move issues in project boards using GitHub actions
When someone creates an issue it moves to the project board "To do". Once the developer creates a branch with issue name then...
Read more >Manage issues - GitLab Documentation
Before moving the issue, make sure it does not contain sensitive data. ... If a user is not a member of a project,...
Read more >The duration or work value changed when I assigned a resource
But if you change the number of resources for a task that already has an assignment, Project calculates how much time it will...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Working perfectly good! Thanks!
This should be resolved in
v0.2.1
let me know if you have any problems. Happy to reopen the issue. Thanks again @CiTRuS93!