Can you check out Contributing Feature Requests please and make sure to always state a root problem your having using Phabricator when filing a feature request? Thanks!

Sorry, I'm not sure what I'm missing here.

My root problem is that I cannot know if I can archive (and eventually remove) a panel because I cannot know if it's still in use in any tabbed panels as the Appears On field doesn't list those. Is anything unclear with that?

See also T6018

Panels can be embedded anywhere in Remarkup, not just Dashboards or other Panels. In general we don't expect people to need to actively archive panels. It'd be better for us to understand why you need to do this.

Ha! I didn't notice it was a duplicate. I'll closes this and point to T6018. Thanks!

In general we don't expect people to need to actively archive panels

Ah, ok, that was not clear to me. In fact now that the misunderstanding is clear I can probably explain my root problem better for you:

1. creating a new panel is extremely easy, often by duplicating an existing one where you don't have edit permissions.
2. this spawns *a lot* of similarly named panels
3. the dropdown in the Add Existing Panel dashboard dialog becomes unwieldy
4. making the Appears On field work with the different kinds of usage would enable at least some manual cleanup (T6018)
5. reworking how panels are managed is probably a even better options, but I have literally no idea how that would work

Thanks!

If cleanup is the goal I'd probably opt to build something directly into ApplicationSearch.

Individually going into a panel to assess frequently seems like quite a workload.

Sure, but in my case they were just freshly created, so the situation was different.

You're right and the root problem is probably with panels management as a whole. Feel free to reopen, I guess for the moment I'll live with the long Add Existing Panel dropdown. :)

Is it ok for me to retitle this feature request?

In T11449#189499, @em wrote:

Is it ok for me to retitle this feature request?

yes. of course :)

See also T7216, which I plan to solve primarily via T5307. This isn't too closely related, but is a somewhat-similar Dashboard configuration usability issue.

Thanks @epriestley!