Ability to add skills ad-hoc at org level during activity create/edit

[smille1834]

When creating an Activity, I realized I needed to add new skills to the drop down for that activity. I opened a new tab, went to skills and added skills I needed, but they didn't translate back to the Activity tab. I had to hit refresh and lost all the information I had input. Could we make it so the skills become available w/out refreshing, and/or create an option to add new skill in drop down in the Activity tab?

[mheggeseth]

I'm not sure the app would actually need something like this. Skills can only be maintained by site admins whereas activities will be managed almost exclusively by org admins. So I suspect that jumping from activity edit to skill edit would not be a common user workflow.

[tonysurma]

@mheggeseth this brings out a latent requirement that is okay for now but will be a rapid priority soon after private preview. Skills will be primarily started as site admins as you said but what I discovered talking to @smille1834 and @OhMcGoo and thinking it through is each org has the potential to want to add additional skills on top of the common ones as different orgs and types of orgs will have unique skills to represent.

So I would make this issue: ability to create skills ad-hoc from drop down in activity tab (removes the refresh need mostly) and then a supporting issue about having skills also at the org level.

[mheggeseth]

Ah, I see. Thanks, @tonysurma.

[mheggeseth]

@tonysurma @BillWagner You can assign this and #317 to me.

[mheggeseth]

Shopping list:

• Add "Create New" link/button to Required Skills section on the Activity Event Create/Edit view
• "Create New" button brings up modal to create a new skill. New skill will be associated with organization related to the current activity.
• New skill will be submitted to Skill Controller via AJAX request.
• Successful skill submission will add the new skill to the list of available skills (viewModel.requiredSkills) in the view without needing to refresh the page.

Sundries:

• Create Activity Event view should only include skills owned by the organization associated with the current Event (in addition to site-wide skills)
• Rename "Delete" action to "Remove" to avoid confusion with deleting a skill from the database

[BillWagner]

@smille1834 @OhMcGoo Can you comment on @mheggeseth list above? Is that the right set of requirements?

[jim-mcgowan]

I'll sit down with @smille1834, today, and we'll come up with a 'unified' response. Thanks for flagging this for us @BillWagner.

[tonysurma]

Just to add to what @smille1834 and @OhMcGoo will say I think your list is spot on with one minor change (which may be what you meant). For the first sundry it should be: "Create Activity view should only include skills owned by the organization associated with the current activity merged with site level skills" IOW the list should include site level skills, skills from current activity org and not those from any other org.