Explainable mapping

Project Task mapping

Tasks are mapped to your project based on how you completed the project survey. Tasks may be added to your project through project survey Match Conditions, project survey Hidden Answers, being carried over across releases, and so on.

The details of these mappings can be viewed from the project Task list and its details.

View Task mapping from the Project Task list

Access the project Task list to view all of the details about how a Task is assigned to your project.

  1. Browse to the Tasks tab of your project to view the project Task list.

  2. From this list, search for a project Task.

  3. Place your cursor over the right side of the project Task to see more information.

    Explainable Mapping 1a
  4. Click on the icon for 'Why is this Task included?'.

    Explainable Mapping 1c

This section provides details about how this project Task was mapped to your project.

Generate a project report with Task mapping details

Project reports can be generated in a comma separated value (CSV) file with information about why a Task was assigned to your project.

  1. Browse to the Reports tab of your project to view reporting options.

  2. Select All Tasks Report.

  3. Under Format, select CSV.

  4. Under Why is this Task included?, check the box for Show reasons why Tasks belong to this project.

  5. Click Download.

The report is generated with a column for 'Why is this Task included?'.

Hidden Answers

Items of the survey can activate or inactivate other items of the survey. For example, the answer “mobile technologies” in the Platform and Language section of the survey is activated if the “mobile client” in the Application General section is chosen. If it isn’t chosen, the “mobile client” is deactivated and cannot be chosen for the project.

Answers in the survey can be selected in two ways: explicitly (manually checked), and implicitly (implied by logic). Implied answers can be both hidden from or visible to you. The advantage of hidden implied answers is that they cannot be explicitly changed in the survey (manual clicking). However, they can still be changed by the project survey’s applicability conditions, or by deselecting the answer that implies it.

Hidden implied answers help with assigning only one answer to a Task instead of having too many answers associated with it.

For example, imagine that a Task is applicable when the application has a web application interface. It can be a mobile application with a web interface, or an application whose “application type” is “web application”. In this case, having a hidden “Generic Web App” can help you assign only one answer to the relevant Tasks.

In this example, these two questions imply a third question, as shown below:

Answer 4: Type of Application: Web application Answer 1079: Involved Components: Includes a web application component

Implication: Answer 1080:Internal Properties: The application is a generic web application.

Only the last answer should be assigned to a Task. The effect is that, regardless of whether Answer 4 or Answer 1079 is checked, Answer 1080 will be true.

For more information about implied answers, see Understanding the project survey.

results matching ""

    No results matching ""