New extension for issues and tasks tracking!
Completely new capability added to the Portal with the new Item Manager.
Users can now add directly in the Portal items such as issues, tasks, risks, activities or others regardless the terminology. This come with a setup feature of all the items and its purpose is to easily map the customer needs in terms of naming and item content fields, to be easily recognized inside each company.
The items may have status, priority, effort, impact, dates or many more and this is completely configurable through a supplied file based on customer specifications and partially configurable item types directly in the Portal. The future releases will come up with fully configurable screens for the list of values that belongs to the fields inside the item types.
The item types setup can be done in such way to include or exclude fields, to mark fields as mandatory or to autocomplete the default value of a dropdown field.
The items could be filtered by their attribute values or searched by title or number. The visibility of the items can be set individually for Internal users only and/or to belong to a particular Partition of a Project. A particular item may have an owner that is responsible for it and an assignee that may be in charge with the completion of the item.
The users may comment on the item, may attach files and may see the audit logs with specific descriptions of the historical changes of it.
A. On a new environment
Please follow the steps from Readme.md file '<checkout-folder>\Source\Web\Portal\Readme'
B. On an existing enviroment
- The new Portal extension ItemMgr requires also updating the Portal itself with MigFx_Portal database
- The following steps are selected from Readme.md file from '<checkout-folder>\Source\Web\Portal\Readme'
- Create a database for the MigFx ItemMgr extension
### Generate database migration scripts
- Run the following commands from `<checkout-folder>/Source/Web/Portal`
dotnet ef migrations script --idempotent --project .\Source\Portal\Api\MigFx.Portal.Api.Infrastructure --startup-project .\Source\Portal\Api\MigFx.Portal.Api\ -c PortalDbContext --output ./portal.sql
dotnet ef migrations script --idempotent --project .\Source\Extensions\ItemMgr\MigFx.ItemMgr.Api.Infrastructure --startup-project .\Source\Extensions\ItemMgr\MigFx.ItemMgr.Api -c ItemMgrDbContext --output ./itemMgr.sql
- Execute the generated `portal.sql` on the MigFx Portal database
- Execute the generated `itemMgr.sql` on the MigFx ItemMgr extension database
### Generate seed data for Item Manager extension
- Locate `SeedSettings.sql` file in `<checkout-folder>\Source\Web\Portal\Source\Extensions\ItemMgr\MigFx.ItemMgr.Api.Infrastructure\Data\Seed`
- Execute the generated `SeedSettings.sql` on the MigFx ItemMgr extension database
## Build Portal and Extension
- Run the following scripts from `<checkout-folder>/Source/Web/Portal`
- Move the content of the generated 'build-output' to the `Physical Path` of the IIS site
- Set the appsettings in `appsettings.json`
"MigFxItemMgr": "<connectionstring to the ItemMgr extension database>"
### Redeploy Client DLLs
- Replace MigFx.Migration.Client.dll and MigFx.IssueLite.Client.dll from generated 'build-output' to the `Physical Path` (this update is needed only because of updating the labels of 2 menu items)