The discussion revolves around a technical issue with setting the same tag for both ‘Watching’ and ‘Tracking’ in the Tags default notification settings within a group. michnpet reports a 500 error due to a database constraint violation, as the system prevents assigning the same tag to both notification types. Moin and SaraDev confirm this is intentional, as a tag can only be set to one notification state at a time. michnpet suggests improving the error message to clarify this limitation, and SaraDev acknowledges the feedback and notes it will be reviewed internally.
Hello,
if I want to set Tags default notification in Group > some group > Manage > Tags I cannot save same tag for Watching and Tracking. I get 500 error
In Logs I can see “ActiveRecord::RecordNotUnique (PG::UniqueViolation: ERROR: duplicate key value violates unique constraint “idx_group_tag_notification_defaults_unique”
DETAIL: Key (group_id, tag_id)=(46, 46) already exists.”
If I select different tags for Watching and Tracking then it is working fine.
Is it bug or I cannot have same tag for Watching and Tracking? According to description they do different things.
Maybe one more thing. Would it be possible somehow improve error message? Error 500 - Internal Error can be a lots of things but here the problem is that you cannot set same labels. We spent some time to find root cause and solution is that it is not possible set. It would save time for users.
I’ve shared this with our team internally so we can look into making some improvements here relating to the error message you were getting in this situation.
