We started using this a few weeks ago and this looks like a very intuitive tool. My management team is very interested in using this with one of our execs fully engaged with the app. I am trying to find a way around what I think is an unfortunate limitation associated with Team Managed projects. In the workflow transitions we would like to force users to populate certain fields but there appears to be no way to force this. Any thoughts or suggestions?
Thanks @Tanguy Crusson I was afraid that would be the case. As I am sure you are aware, users do not always comply with processes that we ask for them to follow. Generally if there are rules set in transitions, we can and do get compliance. At least they are forced to enter something even if it is not the correct option. It is really just to get users who may not be as familiar with the process to learn to follow it better.
Thanks @Billy Turner , would you mind sharing more about the process you're trying to set up? It would really help a lot. Thanks!
Our execs are trying to come up with solid workflow for the ideation processes. This is expected to then lead to the planning processes. Since we will have several people involved in the workflows, they want to ensure that workflow is adhered to in certain areas so that the ideas are going through a similar process regardless of who is managing each idea.
OK thank you. What do you track as "ideas"? Is that "product requirements"?
And who creates them in the first place? Is it the product team or other teams?
Thanks!
This is a new endeavor for us to us to try to use a tool as part of the ideation phase of product planning. We are trying to create new and exciting changes for how healthcare is delivered. The users can certainly be product owners but can also be execs starting to feed the ideas to product owners. I think that PO's are the most obvious path for the work to lead to before getting translated into stories to begin implementation.