This idea involves allowing users to specify a configuration file which can be picked up by the CLI to run and apply on the different platforms.
Why would we want this?
Suppose that we have a standard way of breaking big tasks? E.g. A marketing project that spans across multiple marketing channels. Some of the standard tasks that would be created:
Prepare campaign design material for Adwords
Prepare campaign design material for Facebook
Create a campaign on Adwords
Create a campaign on Facebook
Prepare for UTM tags for tracking campaigns coming from such sources
Validation of UTM tags that URLs are ok for use
Maybe for every marketing campaign, all of such tasks would need to be created, with respective deadlines.
The tasks would also need to be grouped as one group of tasks which needs to be executed together one after another. Failure in one or several tasks might result in problems to further along the chain
Some things that needs to be considered
How should such tasks be defined in a configuration file?
How to address the concept of grouping the created tasks under a single group
Consider using subtask to do grouping of tasks?
Not all task management applications out there have the concept of subtasks
Should we implement in such a way where applications that have concept of subtasks would be able to handle it as expected but create some sort of tags for task management apps that don't have such a feature
Should we allow configuration such as assignee and expected times etc? Are all of that calculated before being submitted to the task management solutions?
If there is an assignee config, is it by user based? Is it possible to have some sort of team config (e.g. 5 analyst + team lead; each of the task is assigned to an analyst - this would allow us to assign it by role. In case of manpower change, we can switch team config and the automation would run as expected?)
If the task assignment is across department? e.g. Creating a marketing campaign might involve making a micro-site which specially list products from a sale, so it might involve the engineering team, who will usually manage the tasks from github or bitbucket or issue managers etc. However, overall lead of the project has to be someone from the marketing site who would need to coordinate the project from start to finish
If such scenario is expected, then would
Naive implementation
Create the ability to list the tasks in the primary tool (no sub task implementation)
This idea involves allowing users to specify a configuration file which can be picked up by the CLI to run and apply on the different platforms.
Why would we want this?
Suppose that we have a standard way of breaking big tasks? E.g. A marketing project that spans across multiple marketing channels. Some of the standard tasks that would be created:
Maybe for every marketing campaign, all of such tasks would need to be created, with respective deadlines.
The tasks would also need to be grouped as one group of tasks which needs to be executed together one after another. Failure in one or several tasks might result in problems to further along the chain
Some things that needs to be considered
Naive implementation