I think we should remove C and I from branch names and just use the issue/ticket id only because in many cases it's not clear at first glance if a task should be considered continuous development or an incident and it should not be defined and locked down by naming the branch. The information about the category of the issue/ticket should be kept (and maintained/updated) in the ticketing system, not in the branch name. What do you think @tharna ?
I think we should remove C and I from branch names and just use the issue/ticket id only because in many cases it's not clear at first glance if a task should be considered continuous development or an incident and it should not be defined and locked down by naming the branch. The information about the category of the issue/ticket should be kept (and maintained/updated) in the ticketing system, not in the branch name. What do you think @tharna ?