Remaining Job and Match profile work, part 2
Description
Priority
Fix versions
Development Team
Assignee

Solution Architect
Parent Field Value
Parent Status
defines
is defined by
relates to
Checklist
hideTestRail: Results
Activity

Ann-Marie Breaux December 16, 2019 at 11:14 PM
Remaining work split from this feature and moved to

Ann-Marie Breaux October 2, 2019 at 5:51 AM
Discussion from Slack:
Ann-Marie Breaux:
I'm not sure if this will save us a ton of development work, but I'm looking for any savings where I can find them. On the "choose jobs" screen, we're aiming for a user to be able to select an existing job or to build a new job on-the-fly. If we built it so that you could only choose an existing job to start with, and then added the functionality for building a new job on-the-fly, would that be acceptable? Or do we need the on-the-fly functionality from the very beginning?
Jenn Colt
Is the alternative that you have to go into settings to build a new job? that seems fine to me. i think some friction around adding jobs will cut down on noise. This might also make perms easier? Only people with settings perms could make jobs but anyone with import perms can run them?
Ann-Marie Breaux:
Hi Jenn Colt - yes, correct - you would need to make sure you created the job (and its match/action/mapping details) in Settings, and then import the file and assign the existing job profile. Good point about perms - so far we have't done anything with perms. I'll add a feature as a placeholder for perms.
Jennifer Eustis:
I agree with Jenn. As long as there is an alternative to adding on the fly jobs, this seems fine.
Christie Thomas:
I agree as well. Jenn makes a great point about permissions, and this is the way that it works in our current system. After the initial set up of the batch loading profiles, we rarely need to create new jobs. Maybe one every month or two?
Jennifer Eustis:
What we change more often are the fixes - though this is only about once a year or less. Fixes are like the mapping profiles where we specify what should be created in terms of fields and what should be added/removed, etc. We try to use old profiles and then create these Aleph fixes for new situations that can be used with those profiles.
Ann-Marie Breaux:
Good - that all makes sense to me, and matches what I've been thinking.

Ann-Marie Breaux September 30, 2019 at 8:32 AMEdited
Consider moving all "Export" profile stories to a new feature, and make it lower priority; talk with SMEs about it

Ann-Marie Breaux September 30, 2019 at 8:31 AM
Broke out the remaining work from Q3 2019 () to this new feature; most work is to complete the match profile screen, then hook up to the job profile.
Details
Details
Reporter

PO Rank
Analysis Estimate
Analysis Estimator

Front End Estimate
Front End Estimator

Front-End Confidence factor
Back End Estimate
Back End Estimator

Captures the remaining work for Job and Match profiles; remaining stories moved from
General topics covered:
Job profiles
Final details of assembling job profiles
Deleting
Exporting
Linking match and action profiles to job profiles
Match profiles
Final details of defining match profiles
Delete
Export
Related job profile header actions
Linking to job profiles
UI buildout
Finish assign jobs screen (allow for assigning existing profiles or creating new ones)
NOTE: Discussion with the Data Import subgroup: we can wait until post-MVP for a way to create a profile on-the-fly on the "choose jobs" screen. For now, assume all profiles are created in settings. See Slack convo in the comments below.