id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
15964	Do not order admin actions by description	Julien Phalip	nobody	"I'm currently dealing with a site where the admin user needs to follow a step-by-step process:

1. Mark selected translations' status as ""New""
2. Mark selected translations' status as ""Needs translation""
3. Mark selected translations' status as ""No translation needed""
4. Mark selected translations' status as ""In progress""
5. Mark selected translations' status as ""Ready for review""
6. Mark selected translations' status as ""Approved""

Therefore I've logically done the following:

{{{
#!python
class MyModelAdmin(ModelAdmin):
    actions = [mark_new, mark_needs_translation, mark_no_translation_needed, mark_in_progress, mark_ready_for_review, mark_approved]
    ...
}}}

But unfortunately the actions are automatically alphabetically ordered by description in the admin interface, i.e.:

1. Mark selected translations' status as ""Approved""
2. Mark selected translations' status as ""In progress""
3. Mark selected translations' status as ""Needs translation""
4. Mark selected translations' status as ""New""
5. Mark selected translations' status as ""No translation needed""
6. Mark selected translations' status as ""Ready for review""

This is not only confusing but also quite inflexible. I think the developers should be responsible for controlling the ordering of actions, similarly as they can control the ordering of `list_display` or `list_filter` fields.

This current behaviour doesn't seem to even be tested. Apparently the action's `short_description` behaviour isn't tested either. The attached patch rectifies this behaviour and adds tests to cover all this."	Bug	closed	contrib.admin	1.3	Normal	fixed			Ready for checkin	1	0	0	0	0	0