Make the number of tags unlimited for the end point

make the number of tags unlimited for the end point and make it available for markdown files to connect with tags
I found it out when I there was 20 tags then i added another one, and it removed all the tags :smiling_face_with_tear:

Thanks for the feedback.
It would be helpful if you could provide your steps and screenshots.

Here are the steps I made




Received your operation screenshot, but can not reproduce your phenomenon for the time being.
My current version is 2.6.12, and I will continue to look at this issue.
For the lost data, you can try to recover it in the endpoint change history.
For detailed information, please check here:Endpoint change history - Apidog Docs

My current version is also 2.6.12.
here I have 20 tags in my endpoints, if I try to add the 21th from the edit tab in the endpoint it returns an error and doesn’t save.
but if I try to add the tag by selecting the endpoint from its folder it removes all the tags
note: at the moment that I recorded the video the maximum limit became 19

My current version is also 2.6.12.
here I have 20 tags in my endpoints, if I try to add the 21th from the edit tab in the endpoint it returns an error and doesn’t save.
but if I try to add the tag by selecting the endpoint from its folder it removes all the tags
note: at the moment that I recorded the video the maximum limit became 19
video.mp4|x
video.mp4|x

This is the procedure I am trying to restore, are our steps similar?
img_v3_02eh_579dcbce-7435-4280-868b-5c851be85ecg.gif
img_v3_02eh_579dcbce-7435-4280-868b-5c851be85ecg.gif

Yes, they are the same. Except for the tag names are longer but I don’t know if that is the issue

This issue has been fixed, please try it. After investigation, we found that the issue was caused by the tag names are longer.

Has the fix been released yet?

Yes, you can try it now.

Thanks, it thows an error now and doesn’t remove the tags 🩵

But also consider expanding the maximum limit

In what situations is it necessary to use long tag names, and how are these tag names designed?

In my current case i designed an endpoint that is used in multiple user stories, also multiple web services and mobile apps so it would be easier to filter by the service and by the userstory
So I find it a need to add those much tags and with semantic names (and that makes it long sometimes)

sky Thank you for providing more context. I understand you’re using tags to link endpoints with user stories and services, specifically using identifiers like “2.6.12”. The tag length limit is becoming a constraint as your project scales.

To better understand your needs, could you share how often you release new user stories? could you provide an estimate of the expected growth rate for tag length on a weekly or monthly basis?

Additionally, would adding optional fields for the start and end versions of user stories associated with an endpoint, along with the ability to filter by version range, effectively address this limitation?

Finally, could you elaborate on your primary use case for filtering endpoints by version? Is this for streamlining API testing or more for maintaining specific API endpoint versions?

Well, the growth rate is often weekly but I don’t understand what the rate can change in the tags field length.
Isn’t it a stand alone validation on the field length no matter how often I update it?

Since me and my coworkers are using another tool for managing user stories, it’s distracting to add fields to the user story

for streamlining API testing & debuging
didn’t use multiple versions, I’m working CI/CD…

Thanks for the feedback.
It would be helpful if you could provide your steps and screenshots.