Consider inherited values when copying workspace settings for workspace templates

Who would benefit?

Any users creating a workspace template from an existing workspace.

What impact would it make?

Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings.

For example, at the workspace level if epics are set to inherit their enablement from their line level, when the template is created epics will display as disabled.

How should it work?

If a setting is set to inherit, look at the inherited value to configure within the workspace template.