|
If you were logged in you would be able to see more operations.
|
|
|
Pulse
Created: 22/Jul/08 06:00 PM
Updated: 05/Aug/08 08:04 AM
|
|
| Component/s: |
Resources
|
| Affects Version/s: |
2.0.8
|
| Fix Version/s: |
2.0.10
|
|
|
Pulse's indicator that a resource has been assigned the "default" version is a null field. I find this confusing as follows:
- When I review a resource setting and see a blank line my initial thought is that I failed to set the version? I am forced to remember that blank = default
- When I set a resource and select browse and then choose default, the version field contains nothing leaving me wonder if my entry was accepted.
I think it would be a significant usability improvement if this was clarified by having Pulse display [default] or something similar rather than en empty space
|
|
Description
|
Pulse's indicator that a resource has been assigned the "default" version is a null field. I find this confusing as follows:
- When I review a resource setting and see a blank line my initial thought is that I failed to set the version? I am forced to remember that blank = default
- When I set a resource and select browse and then choose default, the version field contains nothing leaving me wonder if my entry was accepted.
I think it would be a significant usability improvement if this was clarified by having Pulse display [default] or something similar rather than en empty space |
Show » |
|
Improvement
Resolved
Minor
Make it clearer when a resource value is set to "default"
I presume you are referring to resource requirements here? This sounds like a good idea - we can certainly update the table display to say "[default]" when no specific version is given. Changing the behaviour of the form is trickier: although we could make it more explicit by using an extra checkbox to indicate if you want the default version or not which controls the availability of the version field.