Chester Dias: Please edit the ticket - please read following!
- Refine the title to state the actual task to be done - use imperative voice, same as with git commit messages.
For example:
- "Investigate: Can ansible plugins help us to solve appstore-playbook bug reported in
IGBF-2311?"
or
- "Investigate using ansible plugins to solve appstore-playbook bug reported in
IGBF-2311"
Then, in the description, explain why it is necessary to perform the task.
For example, you might write something like:
"Currently, ansible playbooks used to provision new app store sites are failing to execute. (See IGBF-2311.) The main problem seems to be [whatever the problem is]. One potential solution is to use ansible plugins, which are [summarize what they are]. These could be useful because [explain what prompted you to look into them as a possible solution]."
(The above may not be correct – I do not actually know why you are investigating plugins apart from being interested in it.)
Then, describe what is needed to be done to complete the task. In describing what is needed to be done, be specific enough so that the person who does the task and he person who does the first-level review will be able to understand and review what was done. Try to leave as little doubt as possible as to what the goals of the ticket are.
Last but not least, estimate how long it will take to finish the task in units of "story points." The current estimate - 0.5 - sounds good!
Ansible plugin offers a chance at improving the architectural and design aspect of the core functionalities provided by ansible.
Below are links to the ansible plugins
https://docs.ansible.com/ansible/latest/plugins/plugins.html
Some of the explored plugins were callback plugins which help in modifying and improving the visible aspects of the console messages
like for example the
skippy and full_skip provides the ability to remove the skipped debug messages that occupy the area of the output
the skipped messages can sometimes use too much space as observed in the IGB-2311