13634794100

Committed 03 Mar 2025 03:19PM UTC coverage: 2.067% (-0.1%) from 2.21%

Build # 13634794100

Build Type

push

github

Committed by

web-flow

Commit Message

~ Try coveralls action

Run Details

140 of 6773 relevant lines covered (2.07%)

0.03 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

0.0

/src/Schema/TargetToSourcesMapping.php

<?php

namespace Jira\Client\Schema;

use Jira\Client\Dto;

/** An object representing the mapping of issues and data related to destination entities, like fields and statuses, that are required during a bulk move. */
final readonly class TargetToSourcesMapping extends Dto
{
    public function __construct(
        /**
         * If `true`, when issues are moved into this target group, they will adopt the target project's default classification, if they don't have a classification already.
         * If they do have a classification, it will be kept the same even after the move.
         * Leave `targetClassification` empty when using this
         * 
         * If `false`, you must provide a `targetClassification` mapping for each classification associated with the selected issues
         * 
         * "Benefit from data classification"
         * 
         * @link https://support.atlassian.com/security-and-access-policies/docs/what-is-data-classification/
         */
        public bool $inferClassificationDefaults,

        /**
         * If `true`, values from the source issues will be retained for the mandatory fields in the field configuration of the destination project.
         * The `targetMandatoryFields` property shouldn't be defined
         * 
         * If `false`, the user is required to set values for mandatory fields present in the field configuration of the destination project.
         * Provide input by defining the `targetMandatoryFields` property
         */
        public bool $inferFieldDefaults,

        /**
         * If `true`, the statuses of issues being moved in this target group that are not present in the target workflow will be changed to the default status of the target workflow (see below).
         * Leave `targetStatus` empty when using this
         * 
         * If `false`, you must provide a `targetStatus` for each status not present in the target workflow
         * 
         * The default status in a workflow is referred to as the "initial status".
         * Each workflow has its own unique initial status.
         * When an issue is created, it is automatically assigned to this initial status.
         * Read more about configuring initial statuses: "Configure the initial status | Atlassian Support."
         * 
         * @link https://support.atlassian.com/jira-cloud-administration/docs/configure-the-initial-status/
         */
        public bool $inferStatusDefaults,

        /**
         * When an issue is moved, its subtasks (if there are any) need to be moved with it.
         * `inferSubtaskTypeDefault` helps with moving the subtasks by picking a random subtask type in the target project
         * 
         * If `true`, subtasks will automatically move to the same project as their parent
         * 
         * When they move:
         * 
         *  - Their `issueType` will be set to the default for subtasks in the target project
         *  - Values for mandatory fields will be retained from the source issues
         *  - Specifying separate mapping for implicit subtasks won’t be allowed
         * 
         * If `false`, you must manually move the subtasks.
         * They will retain the parent which they had in the current project after being moved.
         */
        public bool $inferSubtaskTypeDefault,

        /**
         * List of issue IDs or keys to be moved.
         * These issues must be from the same project, have the same issue type, and be from the same parent (if they’re subtasks).
         * 
         * @var ?list<string>
         */
        public ?array $issueIdsOrKeys = null,

        /**
         * List of the objects containing classifications in the source issues and their new values which need to be set during the bulk move operation
         * 
         *  - **You should only define this property when `inferClassificationDefaults` is `false`.**
         *  - **In order to provide mapping for issues which don't have a classification, use `"-1"`.**
         * 
         * @var ?list<TargetClassification>
         */
        public ?array $targetClassification = null,

        /**
         * List of objects containing mandatory fields in the target field configuration and new values that need to be set during the bulk move operation
         * 
         * The new values will only be applied if the field is mandatory in the target project and at least one issue from the source has that field empty, or if the field context is different in the target project (e.g.
         * project-scoped version fields)
         * 
         * **You should only define this property when `inferFieldDefaults` is `false`.**
         * 
         * @var ?list<TargetMandatoryFields>
         */
        public ?array $targetMandatoryFields = null,

        /**
         * List of the objects containing statuses in the source workflow and their new values which need to be set during the bulk move operation
         * 
         * The new values will only be applied if the source status is invalid for the target project and issue type
         * 
         * **You should only define this property when `inferStatusDefaults` is `false`.**
         * 
         * @var ?list<TargetStatus>
         */
        public ?array $targetStatus = null,
    ) {
    }
}

1	<?php
2
3	namespace Jira\Client\Schema;
4
5	use Jira\Client\Dto;
6
7	/** An object representing the mapping of issues and data related to destination entities, like fields and statuses, that are required during a bulk move. */
8	final readonly class TargetToSourcesMapping extends Dto
9	{
10	public function __construct(	×
11	/**
12	* If `true`, when issues are moved into this target group, they will adopt the target project's default classification, if they don't have a classification already.
13	* If they do have a classification, it will be kept the same even after the move.
14	* Leave `targetClassification` empty when using this
15	*
16	* If `false`, you must provide a `targetClassification` mapping for each classification associated with the selected issues
17	*
18	* "Benefit from data classification"
19	*
20	* @link https://support.atlassian.com/security-and-access-policies/docs/what-is-data-classification/
21	*/
22	public bool $inferClassificationDefaults,
23
24	/**
25	* If `true`, values from the source issues will be retained for the mandatory fields in the field configuration of the destination project.
26	* The `targetMandatoryFields` property shouldn't be defined
27	*
28	* If `false`, the user is required to set values for mandatory fields present in the field configuration of the destination project.
29	* Provide input by defining the `targetMandatoryFields` property
30	*/
31	public bool $inferFieldDefaults,
32
33	/**
34	* If `true`, the statuses of issues being moved in this target group that are not present in the target workflow will be changed to the default status of the target workflow (see below).
35	* Leave `targetStatus` empty when using this
36	*
37	* If `false`, you must provide a `targetStatus` for each status not present in the target workflow
38	*
39	* The default status in a workflow is referred to as the "initial status".
40	* Each workflow has its own unique initial status.
41	* When an issue is created, it is automatically assigned to this initial status.
42	* Read more about configuring initial statuses: "Configure the initial status \| Atlassian Support."
43	*
44	* @link https://support.atlassian.com/jira-cloud-administration/docs/configure-the-initial-status/
45	*/
46	public bool $inferStatusDefaults,
47
48	/**
49	* When an issue is moved, its subtasks (if there are any) need to be moved with it.
50	* `inferSubtaskTypeDefault` helps with moving the subtasks by picking a random subtask type in the target project
51	*
52	* If `true`, subtasks will automatically move to the same project as their parent
53	*
54	* When they move:
55	*
56	* - Their `issueType` will be set to the default for subtasks in the target project
57	* - Values for mandatory fields will be retained from the source issues
58	* - Specifying separate mapping for implicit subtasks won’t be allowed
59	*
60	* If `false`, you must manually move the subtasks.
61	* They will retain the parent which they had in the current project after being moved.
62	*/
63	public bool $inferSubtaskTypeDefault,
64
65	/**
66	* List of issue IDs or keys to be moved.
67	* These issues must be from the same project, have the same issue type, and be from the same parent (if they’re subtasks).
68	*
69	* @var ?list<string>
70	*/
71	public ?array $issueIdsOrKeys = null,
72
73	/**
74	* List of the objects containing classifications in the source issues and their new values which need to be set during the bulk move operation
75	*
76	* - You should only define this property when `inferClassificationDefaults` is `false`.
77	* - In order to provide mapping for issues which don't have a classification, use `"-1"`.
78	*
79	* @var ?list<TargetClassification>
80	*/
81	public ?array $targetClassification = null,
82
83	/**
84	* List of objects containing mandatory fields in the target field configuration and new values that need to be set during the bulk move operation
85	*
86	* The new values will only be applied if the field is mandatory in the target project and at least one issue from the source has that field empty, or if the field context is different in the target project (e.g.
87	* project-scoped version fields)
88	*
89	* You should only define this property when `inferFieldDefaults` is `false`.
90	*
91	* @var ?list<TargetMandatoryFields>
92	*/
93	public ?array $targetMandatoryFields = null,
94
95	/**
96	* List of the objects containing statuses in the source workflow and their new values which need to be set during the bulk move operation
97	*
98	* The new values will only be applied if the source status is invalid for the target project and issue type
99	*
100	* You should only define this property when `inferStatusDefaults` is `false`.
101	*
102	* @var ?list<TargetStatus>
103	*/
104	public ?array $targetStatus = null,
105	) {
106	}	×
107	}

tylernathanreed / jira-client-php / 13634794100

Source File Press 'n' to go to next uncovered line, 'b' for previous

Source File
Press 'n' to go to next uncovered line, 'b' for previous