[wp-meta] [Making WordPress.org] #5943: When you create a glossary in a project, it stays for one set.

[Making WordPress.org]

#5943: When you create a glossary in a project, it stays for one set.
--------------------------------------+--------------------
 Reporter:  NekoJonez                 |      Owner:  (none)
     Type:  enhancement               |     Status:  new
 Priority:  normal                    |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 When you create a glossary inside a project (not the locale glossary), it
 stays in that sub project.

 EG: I created one for a project in the stable set, and it didn't show up
 for the dev set.

 Why do project glossaries work in that way? That means it's possible that
 translations are summited in the other sets with other translations... And
 not only that, you can create conflicting glossaries.

 I think it would help us being consistent in a project, when a project
 glossary is for ALL sets and not for just one set.

 And maybe have an option where you can choose for which sets it's shown,
 if people want to filter it for one or more sets and not all?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5943>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org