After cloning a rule, it's not possible to change "Data to compare" in the new (cloned) rule. Is this by design or a bug?

Comments

fago’s picture

Title: Not possible to change "Data to compare" in cloned rule » Improve labels of rendered action/conditions
Component: User Interface » User interface
Category: support » task

It's by design. However, I think we should improve this a bit by:
- Adjust render() of a condition/action so the 'label' describes what cannot be changed any more.

In case of the condition, we could improve it to say "Compare node:property", for entity_create we could say "Create node". Having that scheme applied consistent to all conditions/actions helps I think.

burlap’s picture

I can understand this, however it makes cloning (or changing rules) a bit useless through the UI. OTOH it might be just me relying too much on workflow-ng ways, while the new Rules seem to follow different use patterns...

fago’s picture

Issue tags: +UX

adding tag

mitchell’s picture

Status: Active » Postponed (maintainer needs more info)

I need to figure out how this relates to #1244738: Provide a description field to organize this.

@burlap: What were workflow-ng's ways?

fago’s picture

Component: User interface » User Interface
tr’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (won't fix)

I don't see anything left to do here. The "Data to compare" is fixed when the condition is created and added to the Rule - this has nothing to do with cloning. The data conditions seem to be the only ones where a parameter gets fixed. Regardless, there has been no participation from the community in almost 6 years and there doesn't seem to be any interest in adding this to D7 Rules this late in the D7 development cycle.

If you have a specific proposal and can contribute a patch, please open a new issue.