[ FEATURE REQUEST ]: Ability to configure what needs to be attached to a project/moved and what is not

[VladyslavBilomeria]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe

The ability to move linked issues with the PR is great!
But in my case, I don't need to attach PRs to the project and therefore don't need to put them in any columns.

Describe the solution you'd like:

It would be great to be able to configure whether to attach a PR to a project / move it or not.
Perhaps something like:

attach_pr: false # Specifies whether to attach a PR to the project (if not already attached)
move_pr: false # Specifies whether to move the PR

Describe alternatives you've considered

No response

Additional context:

No response

[leonsteinhaeuser]

@VladyslavBilomeria thank you very much for the feedback and the feature request. I think the described functionality should not be that difficult to implement. I will try to take a look at it in the next few days.

[VladyslavBilomeria]

Great, thank you!

[leonsteinhaeuser]

I had some time to think about this again in the last few days. Separating Issues from Pull Requests would require a lot of effort and code, since GitHub treats Pull Requests as Issues. We could provide a more generic selection like:

move_linked: true/false # if true, attach_linked must be true as well
attach_linked: true/false

[goldiegadde]

yes a generic selection sounds like a good idea.
We currently use multiple project boards for managing issues, and while the functionality to update project attributes is great, I cannot use this automation on issues that belong to different project boards.
Is there any plans to fix this soon ?