[Create/edit survey] Add "job types" (hard-coded templates)

[gino-m]

@jo-spek @lecrabe @kenstershiro @rfontanarosa Building on the idea of "templates":

What if Ground supported a few predefined "job types" - rather than entering a job name, the user could select from a list of job types ("EUDR reporting", ..., "Custom"). We can then auto-populate the job name, the required tasks, the job strategy (predefined vs. ad hoc sites), and selected integrations (Whisp, EUDR). The user could then edit the tasks or job name themselves, or accept the default. The type of job could also be used to collect metrics on how Ground is being used.

Any thoughts?

[jo-spek]

Sounds like a pretty neat solution! Like having a drop-down menu or something in the job creation section to add predefined jobs?

How are the survey questions of a job stored internally? Would it be easily possible to "export" a template, e.g., as CSV, and import it for another survey? I remember from the Ghana campaign that they would setup multiple surveys which always featured the same questions and answers, with multiple conditionals, making it quite strenuous to rebuild for every survey.

[gino-m]

How are the survey questions of a job stored internally? Would it be easily possible to "export" a template, e.g., as CSV, and import it for another survey? I remember from the Ghana campaign that they would setup multiple surveys which always featured the same questions and answers, with multiple conditionals, making it quite strenuous to rebuild for every survey.

I think for that use case they could rely on the proposed "copy survey" tool (#2122). Wdyt?

[jo-spek]

I think for that use case they could rely on the proposed "copy survey" tool (#2122). Wdyt?

For that Ghana case absolutely! Having an export/import functionality would certainly be cool, too, but that's no priority now.

[gino-m]

I'll set as a P2 for GA for now and remove from pm/ux review unless you feel otherwise.

[kenstershiro]

@gino-m @jo-spek @lecrabe I like the idea, and it feels easier to implement and design than full blown templates. Just calling out that a P2 puts it in position 74 on the Features backlog at the moment, which basically means we won't get to it in the next year or two looking at current feature velocity :-) iirc templating was a fairly high priority, I'll bump this to P1 for now? I'll try and put together a summary of the feature request themes to check the relative prioritization of the top items, it's not very clear in github right now.

[gino-m]

I'll bump this to P1 for now? I'll try and put together a summary of the feature request themes to check the relative prioritization of the top items, it's not very clear in github right now.

Sgtm, thanks Ken!