Add default tasks when creating a project?
Hi,
we think about using youtrack for some kind of projects (not software development projects). These are recurring projects, each of them is very similar to former ones - so it would be great to have a specific set of tasks/issues that will be created when we create one of that projects types.
That means: I have a project template for this kind of project. When I create a concrete project there should be around 30 issues that will be added automatically (some tasks, some features, some ...). It is a complete "set" of tasks for this kind of project - because it will be much easier to throw away some tasks that are unneccessary instead of adding 20 tasks by hand every time (and forget some important)
Is it possible somehow?
Best regards, Alex
Please sign in to leave a comment.
Hi Alex,
Thank you for reaching out. Sure, this is possible using workflows, please refer to https://blog.jetbrains.com/youtrack/2017/12/make-it-workflow-part-4-generating-new-issues/ for further examples.
I believe you can implement it as an on-schedule rule which will run once and create all necessary issues.
Please let me know if it helps.
Thank you for the link, it seems to be a good starting point. I'll have a look at this topic(s) when we are ready to work with youtrack.
Have a good time and stay healthy :-)
Sure, keep safe!
Hi Alex!
May I ask how did you manage to solve your problem?
Hi Alex, Hi Anastasia Bartasheva,
we are interested in the scenario as well.
Cold you please share more details?
is that true, that we can bind the flow to the DateTime in the past(01.01.1979), so that it is always occured one time while the project is created.
Is that possible to add the actions not only for tickets but for projects ("OnProjectCreated")?
BR
Ignat
Hello,
I'm Lena from the YouTrack Team.
I'm afraid it has not been implemented out of the box. However, we have a corresponding feature request about that, so please vote for it: JT-51022 Clone issues during project clone.
Currently, as a workaround, you can do the following: create a project with the required issues. When you create a new project, select all the needed issues and clone them. After that, without de-selecting anything, use the `move to project-name` command to move all issues to the newly created project.
As for the additional question:
This scenario was never tested, and even if it works, we don't recommend relying on it for your work processes because it could stop working without any notifications.
I'm afraid there is no such trigger for the workflow. The workflows were designed to work with issues and react to the changes in issues, but not with the projects.
Please feel free to ask more questions if you have any.