SDLC Application Deployment

tip

Role required: admin.

To deploy the SLDC application, complete the following steps:

1. Install the SLDC application.
2. (optional) Install the SDLC-ITSM integration package.
3. (optional) Deploy the demo data.

Install the SLDC application

To install the SDLC application, install the [SDLC] X.X.X full.sop SOP file, where X.X.X is the application version.

Installing updates

---

When updating the installed SDLC application, additional actions may be necessary. You can find the required information about the installation of a specific version in the relevant article of the Release Notes section.

tip

Role required: admin

Install all versions and patches in order. When updating the installed SDLC application, additional actions may be necessary. You can find the required information about the installation of a specific version in one of the relevant tabs below.

1.1.3

Update version 1.1.2 to version 1.1.3

This update has fixed incorrect system name of a sprint state.

If the Sprint (pda_sprint) table is not empty, perform the following actions after the 1.1.3 update:

1. Import the [SDLC]_STR0003361_Fix_state_for_sprint.sop SOP file.
2. Navigate to System Settings → Server Scripts.
3. Open the Fix incorrect state for sprint script record form.
4. Click Run at the bottom of the form.

These actions must be performed only once and are not required during the subsequent updates of the application.

1.2.1

Update version 1.2.0 to version 1.2.1

This update has introduced the SDLC Task State Change table that stores data on task state changes. The table is populated automatically from the moment the application is updated to the new version. To add the history of task state changes that occurred prior to the 1.2.1 update, complete the following steps immediately after the update is finished:

Create history for existing tasks

1. Import the [SDLC]_STR0003993_Create_SDLC_Task_State_Change_Records.sop SOP file.
2. Navigate to System Settings → Server Scripts.
3. Open the Create history records for tasks script record form.
4. Click Run at the bottom of the form.

Use the records in the Main Log (sys_log) table to monitore the progress of script execution. A record is made in the table after every 500 processed task records. When all task records are processed, the record "Migration script finished" appears in the Main Log.

Depending on the number of records in the SDLC Task table, the script can take some time to be completed. The estimated time to process 10,000 records is 25–30 minutes.

These steps only need to be performed once and are not required during the subsequent updates of the application.

1.3.1

Update version 1.3.0 to version 1.3.1

This patch expands the logic of specifying spent time from the task forms and from the task preview window on project boards. Now when a user specifies the time spent on a task, the system takes into account the limits introduced in version 1.1.1 of the Work and Time Management (WTM) application.

To update the existing time entries in accordance with the changes in the WTM application, complete the following steps:

warning

Before making changes, ensure that the SDLC application is selected in the Admin Preferences of the sidebar.

1. Import the [SDLC]_STR0004547_Update_time_spent_in_SDLC_Tasks_and_Timesheets.sop SOP file.
2. Navigate to System Scheduler → Scheduled Scripts.
3. Open the [SDLC] Update time spent in SDLC Tasks and Timesheets script form.
4. Select the Active checkbox.
5. Select the convenient date and time in the Run date and time field.
6. Click Save or Save and exit to apply the changes.

The script will run at the specified time and update the values of the Total time spent (pda_total_time_spent) in the task records and the records of the Timesheet (wtm_timesheet) table in accordance with the Timecards (wtm_timecard). Use the Main Log (sys_log) to monitor the progress of script execution.

Depending on the number of records, the script can take some time to be completed. The estimated time to process 10,000 records of the SDLC Task table and 1000 records of the Timesheet table is 10 minutes.

These steps only need to be performed once and are not required during the subsequent updates of the application.

Install the SDLC-ITSM integration package

If the ITSM application is installed on your instance and you need to connect it to the SDLC application, install the [SDLC] SDLC.1.2.0_ITSM.1.12.1.sop file and configure the SDLC-ITSM integration. You only need to configure this package once. The data will be preserved at the future updates of the application.

info

Supported application versions:

• ITSM 1.12.1
• SDLC 1.2.0

Deploy the demo data

The SDLC demonstration data package is designed to help a user learn the funcionality and overall logic of the application. The demonstration data include examples of records for all major application tables, as well as records in the Simple Application tables, such as employees with the configured roles. You can use them to explore the appication role system.

Several projects with configured infrastructure will be added to your instance if you upload the demo data. This includes pre-configured boards, examples of products, product modules, tasks of all types and project members.

note

The demo data is only available in Russian at the moment.

The file with the demo data is provided with the application. To deploy the demo data on your instance, complete the following steps:

1. Ensure that SDLC application is installed on your instance. Click the icon in the right upper corner of the screen to open the Preferences menu. Check if the SDLC option is present in the Application drop-down list.
2. Import the JSON file with the demo data.

Records list

---

Demo data (SDLC entities)

• 7 projects (2 projects that use the SCRUM approach and 5 that use the KANBAN approach). There are six products dedicated to the product development, and one is not related to a product. A task board of the corresponding type is available for each project.
• 32 project members (some employees participate in more than one project)
• 5 products
• 18 product modules
• 6 sprints
• 2 releases
• 6 additional attributes for two boards
• 2 areas for two boards
• 12 badges for three boards
• 56 columns for all boards
• 4 swimlanes for three boards
• 6 swimlane rules
• 14 color markers for five boards
• 81 tasks:
  • 16 epics
  • 10 defects
  • 17 user stories
  • 32 general tasks
  • 6 subtasks

Demo data (Simple Application entities)

• 13 employees with pda_user role
• 1 employee with pda_user, pda_admin roles
• 1 company
• 1 location