Project

General

Profile

Actions

Feature #27161

closed

print applied filter on task export

Added by Adam Ruzicka almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1723670

1. Proposed title of this feature request
[RFE] print applied filter on task export

3. What is the nature and description of the request?
There are different filters, some are default, some are configured using ENV variables when running task export. But it's not always clear, what type of filter is applied.

for example:
1) foreman-rake foreman_tasks:export_tasks TASK_SEARCH=all TASK_DAYS=3 -> 16 tasks
2) foreman-rake foreman_tasks:export_tasks TASK_SEARCH='' TASK_DAYS=3 -> 2822 tasks
3) foreman-rake foreman_tasks:export_tasks TASK_SEARCH=ALL TASK_DAYS=3 -> 16 tasks
4) foreman-rake foreman_tasks:export_tasks TASK_DAYS=3 -> 2835 tasks
5) foreman-rake foreman_tasks:export_tasks -> 7396 tasks
6) foreman-rake foreman_tasks:export_tasks TASK_SEARCH='' -> 32153 tasks

4. Why does the customer need this? (List the business requirements here)
To avoid confusion and mistakes

5. How would the customer like to achieve this? (List the functional requirements here)
Print the applied filter when running the command. Similar to cleanup-task

foreman-rake  foreman_tasks:cleanup NOOP=true VERBOSE=true AFTER=60d TASK_SEARCH=''
...
[noop] deleting all tasks matching filter started_at < "2019-04-25 09:12:13" AND state = stopped

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
When the command is executed, it should print the applied filter on stdout.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
no

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
asap

9. Is the sales team involved in this request and do they have any additional input?
no

10. List any affected packages or components.
tfm-rubygem-foreman-tasks

11. Would the customer be able to assist in testing this functionality if implemented?
sure

Actions #1

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/foreman-tasks/pull/428 added
Actions #2

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases foreman-tasks-0.15.0 (Foreman 1.21) added
Actions #3

Updated by Adam Ruzicka over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Adam Ruzicka over 4 years ago

  • Subject changed from print applied filter on task export to print applied filter on task export
  • Fixed in Releases foreman-tasks-0.15.8 added
  • Fixed in Releases deleted (foreman-tasks-0.15.0 (Foreman 1.21))
Actions #5

Updated by Adam Ruzicka over 4 years ago

  • Fixed in Releases foreman-tasks-0.16.1, foreman-tasks-0.17.0 added
Actions

Also available in: Atom PDF