yes, I can see same issue at my end as well. It looks like an issue to me. I will open jira for this.
Hi Abhijit and Fernando. The behavior you have noticed it is not a issue in a fact. As the attribute cancel activity suggests, it cancels the activity (or sub-process) to which is the signal catching intermediate event attached to. If the signal catching intermediate event is attached to some activity (or sub-process) then the attribute cancel activity is stored appropriately. Otherwise it is always stored as true, however it has no influence on the process execution.
Abhijit, could you also please provide a link for the jira if you have raised some already? Thanks.