The Instructure Community will enter a read-only state on November 22, 2025 as we prepare to migrate to our new Community platform in early December. Read our blog post for more info about this change.
Found this content helpful? Log in or sign up to leave a like!
I logged this with Support and was told this was "intended behaviour".
I cannot think of a single use-case where this would be useful to have the same tag names. Please fix this.
Reproduceable following Alex's five step instructions.
I cannot think of a single use-case where this would be useful to have the same tag names.
Imagine a situation where application of tags is automated across thousands of courses. You might find you need multiple system-generated tag_ids which all map to the same semantic meaning. In that case, forced uniqueness on a label field would be extremely frustrating. And then I would have started this thread instead of you. And we would be having the exact mirror-image of this discussion. 😃
There is also a UX aspect to this. It's fairly standard across Canvas that label/informational fields allow duplicates (e.g., course names, user names). From a system design perspective, consistent UX behaviour across many features is (IMO) arguably more important than the implementation details of any one feature.
And we would be having the exact mirror-image of this discussion. 😃
The positions are not mutually exclusive. I took the OP to be about duplicate tags within a group. You're talking about duplicates across the service. Having duplicates within a group could produce unintended consequences further down the line in applying the tags to items. Students emailing course leaders asking why they do not have access to course content, when their peers do, is one I'm thinking of.
Agree there will be consequences down the line.
I had a similar issue when I noticed duplicate tags accidentally created in a single class (created by SIS import). Only one of the tags had users assigned, while the other duplicates had no students. Since our instructors are using tags to assign work to tagged students, the instructor could assign work to a duplicated tag with no students assigned to it instead of the correct one. I really hope the development team would fix this soon to avoid a big support headache in the future.
Ah - that makes sense. So a suitable solution would require uniqueness inside a group, but not across groups.
I have a similar situation. If I create a single tag for a course via SIS upload, then reupload the same csv file, the class now has:
1. One tag with the same name
2. One tag set with the same name
Do note, nothing in the csv file changed between the first two uploads. The headers of the file are simply:
| tag_id | course_id | name | status |
Community helpTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in