Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

By default, display active efforts when using an "Objectives / Effort" filtered search #3123

Closed
dspCarlson opened this issue Aug 4, 2020 · 1 comment · Fixed by #3125
Closed

Comments

@dspCarlson
Copy link

dspCarlson commented Aug 4, 2020

Is your feature request related to a problem? Please describe.
A filtered search for "Objective / Efforts" displays active and inactive efforts together with the inactive efforts being initially visible. For example, if a search for an effort with the word "Logistics" is executed, the inactive efforts are displayed first. This is confusing to users. It's frustrating for the users to go back and select the "Status" filter.

Describe the solution you'd like
When the "Objectives / Effort" ribbon is chosen for a filtered search, the "Status" filter should automatically be displayed with a value of "Active."

A clear and concise description of what you want, formulates as a user story:
It should be clear to users that they are choosing active efforts when using a filtered search. Users seldom if ever want to see the inactive efforts in a filtered search.

Describe alternatives you've considered
N/A

Additional context
N/A

@dspCarlson dspCarlson changed the title By default display active efforts when using a "Objective/Effort" filtered effort By default, display active efforts when using an "Objectives / Effort" filtered search Aug 4, 2020
@VassilIordanov VassilIordanov mentioned this issue Aug 5, 2020
14 tasks
@dspCarlson
Copy link
Author

Implemented in release 2.1.27-285 on 11 August 2020. Closing the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants