Is there a way to alphabeticaly order teams in the left panel?

[evanchaoli]

A pipeline admin maybe in a lot of teams, it's hard to locate a team given there is a long team list in the left panel. So is there a way to show teams in alphabetical order in the left panel on the GUI?

[skreddy6673]

Yup, this is so helpful when you logged in as admin.

[vito]

Hmm, we'll be working on a 'favoriting pipelines' feature soon. Don't know if that would help though. Ordering alphabetically seems sensible - perhaps with teams you're actually a member of listed first. I'm actually not sure what the current ordering is based on.

@matthewpereira Any thoughts on this?

[matthewpereira]

I think alphabetical sorting makes a lot of sense. 👍 We could eventually add a 'sort by recency' or 'sort by number of pipelines in each team' or a number of other options too, with ascending and descending variations.

I'm hoping that some of the view enhancements that are on the roadmap will help, but confusion over how Concourse sorts things has come up a number of times - some bandaid solution to make it more predictable would be great.

[jamieklassen]

I can comment what currently determines the team order. We can see here:

concourse/web/elm/src/SideBar/SideBar.elm

Line 147 in 3b487b5

|> List.Extra.gatherEqualsBy .teamName

that the view function makes use of List.Extra.gatherEqualsBy, and from its documentation:

https://github.com/elm-community/list-extra/blob/4a1b8674db0ddbb84294de01807b373d7a5b06bd/src/List/Extra.elm#L1927-L1928

So the real source of truth is however the backend is sorting the items in the ListAllPipelines response:

concourse/atc/api/pipelineserver/list_all.go

Line 22 in 3b487b5

pipelines, err = s.pipelineFactory.AllPipelines()

which, in the case of a super-admin, is pipelineFactory.AllPipelines:

concourse/atc/db/pipeline_factory.go

Line 75 in 3b487b5

OrderBy("team_id ASC", "ordering ASC").

so the ordering is by team id, and then by the ordering column. Since team_id is a foreign key:

concourse/atc/db/migration/migrations/1510262030_initial_schema.up.sql

Line 391 in 3b487b5

team_id integer NOT NULL,

to an auto-incrementing ID field:

concourse/atc/db/migration/migrations/1510262030_initial_schema.up.sql

Lines 549 to 570 in 3b487b5

	CREATE TABLE teams (
	id integer NOT NULL,
	name text NOT NULL,
	basic_auth json,
	admin boolean DEFAULT false,
	auth text,
	nonce text,
	CONSTRAINT constraint_teams_name_not_empty CHECK ((length(name) > 0))
	);
	CREATE SEQUENCE teams_id_seq
	START WITH 1
	INCREMENT BY 1
	NO MINVALUE
	NO MAXVALUE
	CACHE 1;
	ALTER SEQUENCE teams_id_seq OWNED BY teams.id;

This really means that teams in the sidebar will appear in the order they were created.

[skreddy6673]

I just checked on my end and it's exactly how the teams are displayed.

[evanchaoli]

@vito Should this be converted to an issue?

[vito]

With our new community structure, converting it to an issue would mean it goes on our backlog/roadmap. We've validated the idea, but we don't necessarily have bandwidth for it at this point, so I don't want to set an expectation that this will happen through us implementing it and make everyone wait on us since it's not likely to be a high priority.

That being said, I do see a need for a sort of "Help Wanted" category for things like this, which would previously be done through issues. Once Discussions supports categories we could make one for it. Hopefully that's sometime soon. 🙏

[evanchaoli]

Okey, let me submit a PR.

[evanchaoli]

My PR #5622 has been merged.