Is it ok to make BURs with only one tag? I've discovered the hard way that you can't edit or reject
a pending tag alias and implication when you request through the other options than
Request BUR.

Also why is that the case? Why I can't edit my own pending tag alias and implications when
done through Request Alias and Request Implication?

And if I can use Request BUR for single tags, then why we have the other options? Aren't
they redundant and clunkier because you can't edit/reject? The only reason I can see for
them is that they are more "user-friendly" because you don't have to deal with scripts?

Could someone help me understand? (๑•﹏•)

sieghelm_lockayer said:
Is it ok to make BURs with only one tag? I've discovered the hard way that you can't edit or reject
a pending tag alias and implication when you request through the other options than
Request BUR.

Also why is that the case? Why I can't edit my own pending tag alias and implications when
done through Request Alias and Request Implication?

And if I can use Request BUR for single tags, then why we have the other options?

BURs are a relatively new option, for users. Before the site revamp, the only way to request aliases and implications was through the Request Alias and Request Implication forms. Multiple alias/implication requests would be done by making one of those requests and then adding a description mentioning the others. If I recall correctly, moderators had access to something like BURs, so a properly formatted description could be copy-pasted into that. The site update included improvements and added safety checks to the BUR system to allow users to make them without a risk of breaking things.

Though there are still oddities with it. For instance, if a BUR tries to make an alias or implication that breaks a normal Alias/Implication Request, you get a warning/error, but a BUR tries to make an alias or implication that breaks another BUR gets no warning or error. The messages generated from bad BURs are also a lot less understandable since it's more technical. Also, I've noticed aliases breaking tag types which I think (though not completely sure) is caused by BUR aliases (at least, I don't remember seeing any mis-typed tags as a result of a plain Alias Request).

watsit said:
(Helpful things! :D)

sieghelm_lockayer said:
Is it ok to make BURs with only one tag?

Now I think this is the only question that still lasts.

sieghelm_lockayer said:
Is it ok to make BURs with only one tag?

Now I think this is the only question that still lasts.

Yes, even if it's just an implication or alias.

-
Thanks Watsit and Clawstripe for helping!

(*˘︶˘*).｡*♡

-

sieghelm_lockayer said:
Is it ok to make BURs with only one tag?

Note that this applies particularly to operations which can only be done through BUR, most notably category changes (to invalid, or for any tag with over 100 posts).

wat8548 said:
Note that this applies particularly to operations which can only be done through BUR, most notably category changes (to invalid, or for any tag with over 100 posts).

Could you then explain the common occurrence of BURs with either only 1 imply or 1 alias, which could be very well requested with the Request Alias or Request Implication options?

sieghelm_lockayer said:
Could you then explain the common occurrence of BURs with either only 1 imply or 1 alias, which could be very well requested with the Request Alias or Request Implication options?

Yes, BURs are better. For example, you can't edit an old-style alias or implication after submitting it, which makes more work for the admins (the main bottleneck) if you got something wrong or the other users disagree with you. I don't think you can self-reject them either, which you can for BURs. In theory the automated check for pending alias/implication requests to prevent conflicts is a good idea, but these days it's starting to create more work than it saves.

wat8548 said:
(Helpful things!)

Wait I think I misunderstood you. You were saying that I also can use BURs to request just one 1 alias o 1 imply? The way I interpreted it seemed more like that I shouldn't be doing that and only using it for operations that a simple request can't handle.

You said "particularly" tho. So I think I just misunderstood what you said, I'm sorry!

Anyways... thanks for contributing to this topic and giving your helpful thoughts! ( ╹▽╹ )👍