1. What is the problem? Why is it a problem?
At the moment, forms can be cloned, but it only does half of the job by not cloning the conditions as well.
We currently have 3 different products (brands), and each product will have 3 forms each (Question, Feature Request, and Bug Form). The bulk of our fields are Modules, submodules, pages related to each submodule, and the actions that can be performed on each page (super granular, I know). But this is all data we have to track. Which means a ton of fields and conditions.
2. How do you solve the problem today?
One brand has 393 fields, and ~200 conditions set. As of now, I will manually have to rebuild all of the conditions.
3. How would you ideally solve the problem?
In a perfect world, the "clone" option on the ticket form would include the conditions as well.
I see how activating duplicated forms can cause an issue. If there was a limitation for activating (not saving, in case someone needs to work on it at a later time) forms that are exactly the same, that may prevent any issues later down the road. (Not sure why someone would need two active forms that are exactly the same.)
4. How big is the problem (business impact, frequency of impact, who is impacted)
Personally, this is a huge nuisance because I spent a ton of time with just one brand and I have two more to go. Hopefully, we don't do a rebuild like this again. But not having the ability to clone everything is going to delay when we would be able to start collecting the data our Board needs.
Hopefully, someone else sees the value in this and can get this implemented. Or if someone can help me on the side, I'd appreciate it! Please let me know if you need any more information!
Iniciar sesión para dejar un comentario.