0
Task Management in the Designer
Introduction
From version 8 on, the Designer User is able to define specific "task" that collect all associated changes to the logicnet model, such that a list of actions can be shared online, or exported for onward distribution. Tasks can be sourced/maintained locally in the data.db (by default) or sourced from a JIRA installation (see System Settings - Designer article).
Description
Immediately (using data.db as a source), or after configuring the Designer for use with JIRA, a Designer User can create a new task by navigating to the Tasks tab of the bottom Designer panel.
- When no tasks exist, the Designer User can complete the fields (Title, Description, State, Assignee) and click SAVE to create one
- State contains system categories and is not customizable at this time
- Assignee is limited to users listed in the User Management module
- To record changes against any task, the Designer User has to select the task from the list and click on ACTIVATE.
- From this point, and until the user clicks on Deactivate, all changelog entries are associated with the task ID
- The ID and title of the task are shown in the header
- The changelog can be exported and/or filtered to show only those changes associated with a specific task.
See Changelog Information in the Designer article for more information.
Designer Configuration
Information about configuring Task Management connected to a JIRA project can be found here.
Like
Follow
Reply