Hello! Actually, I think that we needed to have a broader discussion about what the current properties could and could not do, or what rules you had in mind when you wrote it. This use case came from the following situation: I created a feature and bound some parameters to it, but I did not mark all of the parameters with the 'Parameter feature mandatory' property set to yes. When I then added a group, the feature was moved into the tab-like UI, which I personally found quite convenient. However, there were still some aspects that I did not fully understand. For example, if you assigned two parameters to a feature and marked both of them as mandatory, a radio button appeared that allowed you to select which parameter to use. At the same time, the content of both parameters was still saved and if you marked both of them as mandatory you got the behavior from this ticket. I think that we should have some of the rules written somewhere because there are a bunch of them and if we don't know exactly how they are supposed to interact we will think that there are some feature that don't exist in reality. Also this raised another question: how were we supposed to retrieve the parameter that was actually selected by the user in Velocity?
Farcasi Alexandru-Vicentiu on 12/Mar/26 14:47
Hello! Actually, I think that we needed to have a broader discussion about what the current properties could and could not do, or what rules you had in mind when you wrote it. This use case came from the following situation: I created a feature and bound some parameters to it, but I did not mark all of the parameters with the 'Parameter feature mandatory' property set to yes. When I then added a group, the feature was moved into the tab-like UI, which I personally found quite convenient. However, there were still some aspects that I did not fully understand. For example, if you assigned two parameters to a feature and marked both of them as mandatory, a radio button appeared that allowed you to select which parameter to use. At the same time, the content of both parameters was still saved and if you marked both of them as mandatory you got the behavior from this ticket. I think that we should have some of the rules written somewhere because there are a bunch of them and if we don't know exactly how they are supposed to interact we will think that there are some feature that don't exist in reality. Also this raised another question: how were we supposed to retrieve the parameter that was actually selected by the user in Velocity?
Sorry for the late response I meant to add this details a while ago, but I got carried away with other tasks
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
