...
With dynamic packages, the content and sort order are managed dynamically based on an include path and/or exclude path. The include/exclude paths are regular expressions matching the project file path to determine which project files should be included or excluded from the package. More than one include or exclude path can be defined by adding that new path on the next line. By default, new packages are set to User Managed type, as well as for Salesforce DX packages created from the SFDX.json file.
...
Note that when new files are populated from Project Files tab all dynamic packages are updated accordingly. This can be a big productivity gain when the contents of the package can be derived according to some rules.
Below is an example of a dynamic package that includes all the .profile files of the project.
...
To build a package, go to the execution screen and click Build.
...
Associating Issues to a Package
Packages typically correlate to a smaller subset of work which more often than not relates to an issue in an Issue Tracking System like Jira. Packages that fall in this bucket can link the relevant issues directly to the Package. Doing this saves the hassle of having to mention the issue number in the commit message or manually specifying on the build request form.
| Warning |
|---|
Before Issues can be linked to a Package the Project must inherit or specify its own ITS Configuration. |
To associate Issues to a package, Edit the Package as demonstrated above and in the Related Issues field you can manually enter Issue Numbers. You will also be shown previously linked Issues that FlexDeploy is aware of.
...
Once associated (1), Issues will be automatically associated during the build process (2).
...
Add File(s) from Change Logs
...