Usability: Creating a release of a project, default to current project
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start at the node/add/fserver-release path and inspect how the field_fserver_project value is selected when a release is created. Reproduce the flow by opening a project, clicking “add new release,” and checking the project field. Done means the field defaults to the project identified by the originating URL while still allowing a different project to be selected.
Written by the indexing model from the issue text.
Description
After navigating to a project and then clicking to add a new release (on path node/add/fserver-release), it would be neat if the field_fserver_project field defaulted to the current project (i.e the project one was on when clicking "add new release" and the one defined by the URL ).
A couple of times I didn't check this field and took a moment to realise why my release had been applied to a different project: namely, the alpabetically-first project on my feature server, because it was the default choice in the combobox field.
I don't really know if this is possible to change with CCK (weighting a field based on some argument / condition such as what referer or something) - it'd just be a neat usability thing to know the Release you're making is by default going to apply to the project you were viewing when you clicked 'Add new release'.
Cheers :)
- Dominant language
- PHP
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from developmentseed/FeatureServer
-
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
-
SEO issue: titles Open
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
developmentseed/FeatureServer#9 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
developmentseed/FeatureServer#3 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in developmentseed/FeatureServer
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·