Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Issue/PR the Project, when assigned to a milestone? #26

Closed
GaryJones opened this issue Oct 4, 2018 · 9 comments
Closed

Add Issue/PR the Project, when assigned to a milestone? #26

GaryJones opened this issue Oct 4, 2018 · 9 comments

Comments

@GaryJones
Copy link

Would it be possible to add functionality, such that Issues and PRs assigned to X milestone get put in X project (and then existing rules could presumably automatically put that in a particular column.)?

Right now, the readme suggests that milestoned_issue can only be used to move a card once it has already been added.

What we don't want is to require that all issues automatically get added to a project.

@project-bot project-bot bot added this to To do in Main Project Oct 4, 2018
@janpio
Copy link
Contributor

janpio commented Nov 2, 2018

Did I understand correctly that you are looking for a way to add issues to a project board when they are added to a milestone?

If so, this is definitely not possible right now, the only way to add issues is via new_issue when they are created.

In theory it would be possible to create an "add issue to board when it is added to milestone x.y" of course - but that would probably not really match the current naming.

Can you tell a bit more about the use case behind that? Do you want one project board per milestone?

@GaryJones
Copy link
Author

Did I understand correctly that you are looking for a way to add issues to a project board when they are added to a milestone?

That is correct.

Do you want one project board per milestone?

Yes. Right now, the projects are milestone-based - one project board for 2.7, one for 2.8, one for 2.9, etc.

@janpio
Copy link
Contributor

janpio commented Nov 3, 2018

Can you think of a name for the "trigger" that would somehow match the current scheme? This might be the biggest hurdle right now.

@GaryJones
Copy link
Author

GaryJones commented Nov 3, 2018

I've not looked at the logic, but could milestoned_issue be re-used? i.e. if the board doesn't yet exist on a board, then add it and "move" it to the correct column?

(Aside: there's no milestoned_pullrequest?)

If not, maybe milestoned_issue_add or similar variant?

@janpio
Copy link
Contributor

janpio commented Nov 4, 2018

Reusing doesn't work, something has to tell the code that it should add an issue. So add_milestoned_issue might be a good idea.

But: This of course opens the possibility of further "triggers" to add an issue or PR to a board. Any other useful ones?

(Aside: there's no milestoned_pullrequest?)

Seems so. Best create an issue for it.

@munnerz
Copy link

munnerz commented Nov 6, 2018

+1 for this - I'd love a way to automatically add a PR or Issue to a project when it is added to a milestone, and the inverse, it'd be great to remove it from the project automatically when it is removed from that milestone.

Something like:

milestoned_issue v0.6
demilestoned_issue v0.6

milestoned_pullrequest v0.6
demilestoned_pullrequest v0.6

// The old behaviour of the commands without an arg could be retained.
// This then matches *all* issues/PRs as they are added to any milestone.
milestoned_issue
milestoned_pullrequest

@janpio
Copy link
Contributor

janpio commented Nov 6, 2018

// The old behaviour of the commands without an arg could be retained.

Note that the current implementation only moves already existing items and does not add them to a board. That's why implementing this would be a major new feature for the bot and would probably require a rework on the naming of stuff.

@gannebamm
Copy link

I would like this feature

@sleepylee
Copy link

+1

@GaryJones GaryJones closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2022
Main Project automation moved this from To do to Done Dec 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Main Project
  
Done
Development

No branches or pull requests

5 participants