It is something we have looked into (and we still are). The issue we ran into was that a BluePrint can do a lot of stuff that might not necessarily be compatible with the template that gets applied and you end up with a project that's not totally consistent. For example, a project blueprint might create a bunch of issues and migrate some of them to statusX. If the project template that's being applied then changes the workflow scheme to something that doesn't have statusX - that conflict is very difficult for us to surface to a non-administrator to handle (and might not be something that the creator is prepared to handle).
That said - feel free to drop in an issue at https://wittified.atlassian.net/browse/PCFJ about your use case and we can take another look at it.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.