can you please post the issue here - not just link to other ones.

Can someone on the bug squad please explain why there are now two RFC labels, and why the existing one wasn't just renamed if you wanted to change from the acronym to the fully spelled out name, and why nothing was posted on the issue tracker repo about this maintenance since there are code level integrations in the tracker regarding this label? This seems like someone created more work for themselves for the sake of creating more work.

i tried to use a short one using a Description if you hover but if i delete the long-named label it is automatic assigend again, i guess by using "[RFC]" in title. I can't tell you why this not works so i gave up and live with this circumstances.

This method in the issue tracker checks the title for "[RFC]" on issues, and this method does the same for pull requests. The TL;DR is if you change something that has an issue tracker integration, it needs to be changed in the issue tracker as well otherwise it creates problems.

Solution is to delete the "RFC"-Label and rename the "Request for Comment" to "RFC"?

If you all want the label to be "RFC" then yes, delete the current "RFC" label, rename the "Request for Comment" label to "RFC", and submit a pull request to the issue tracker changing those files to use the new label name. Same goes with any other label managed in those two files.

thanks @mbabker. @Quy can you create a PR as we talked today about that RFC-Issue?

It was mentioned in BS last meeting that there are 2 RFCs. I don't know when the 2nd one got added. If we use Request for Comment label, then we don't need to update issue tracker, but it is not up to me to decide.

I added the second one "RFC" as its shorter and similar to "RTC" - both have a hover Description. So i like the Solution @mbabker wrote but this needs a PR.

PR created joomla/jissues#1060

All the joins got removed in the Workflow revamp