Skip to content

Commit a490d79

Browse files
committed
Few incremental improvements
1 parent 163558f commit a490d79

File tree

4 files changed

+84
-0
lines changed

4 files changed

+84
-0
lines changed

src/version3/models/index.ts

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,7 @@
1+
export * from './workflowSchemeUpdateRequiredMappingsResponse';
2+
export * from './workflowSchemeUpdateRequest';
3+
export * from './workflowSchemeReadRequest';
4+
export * from './workflowSchemeReadResponse';
15
export * from './jiraExpressionEvaluateContextBean';
26
export * from './evaluatedJiraExpression';
37
export * from './configurationsListParameters';
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
import { CustomContextVariable } from './customContextVariable';
2+
import { IdOrKeyBean } from './idOrKeyBean';
3+
import { JexpEvaluateCtxIssues } from './jexpEvaluateCtxIssues';
4+
5+
export interface JiraExpressionEvaluateContextBean {
6+
/** The ID of the board that is available under the `board` variable when evaluating the expression. */
7+
board?: number;
8+
/**
9+
* Custom context variables and their types. These variable types are available for use in a custom context:
10+
*
11+
* - `user`: A [user](https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference#user)
12+
* specified as an Atlassian account ID.
13+
* - `issue`: An [issue](https://developer.atlassian.com/cloud/jira/platform/jira-expressions-type-reference#issue)
14+
* specified by ID or key. All the fields of the issue object are available in the Jira expression.
15+
* - `json`: A JSON object containing custom content.
16+
* - `list`: A JSON list of `user`, `issue`, or `json` variable types.
17+
*/
18+
custom?: CustomContextVariable[];
19+
/**
20+
* The ID of the customer request that is available under the `customerRequest` variable when evaluating the
21+
* expression. This is the same as the ID of the underlying Jira issue, but the customer request context variable
22+
* will have a different type.
23+
*/
24+
customerRequest?: number;
25+
issue?: IdOrKeyBean;
26+
issues?: JexpEvaluateCtxIssues;
27+
project?: IdOrKeyBean;
28+
/** The ID of the service desk that is available under the `serviceDesk` variable when evaluating the expression. */
29+
serviceDesk?: number;
30+
/** The ID of the sprint that is available under the `sprint` variable when evaluating the expression. */
31+
sprint?: number;
32+
}
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
import { MappingsByIssueTypeOverride } from './mappingsByIssueTypeOverride';
2+
import { MappingsByWorkflow } from './mappingsByWorkflow';
3+
import { DocumentVersion } from './documentVersion';
4+
import { WorkflowSchemeAssociation } from './workflowSchemeAssociation';
5+
6+
/** The update workflow scheme payload. */
7+
export interface WorkflowSchemeUpdateRequest {
8+
/**
9+
* The ID of the workflow for issue types without having a mapping defined in this workflow scheme. Only used in
10+
* global-scoped workflow schemes. If the `defaultWorkflowId` isn't specified, this is set to _Jira Workflow
11+
* (jira)_.
12+
*/
13+
defaultWorkflowId?: string;
14+
/** The new description for this workflow scheme. */
15+
description: string;
16+
/** The ID of this workflow scheme. */
17+
id: string;
18+
/** The new name for this workflow scheme. */
19+
name: string;
20+
/**
21+
* Overrides, for the selected issue types, any status mappings provided in `statusMappingsByWorkflows`. Status
22+
* mappings are required when the new workflow for an issue type doesn't contain all statuses that the old workflow
23+
* has. Status mappings can be provided by a combination of `statusMappingsByWorkflows` and
24+
* `statusMappingsByIssueTypeOverride`.
25+
*/
26+
statusMappingsByIssueTypeOverride?: MappingsByIssueTypeOverride[];
27+
/**
28+
* The status mappings by workflows. Status mappings are required when the new workflow for an issue type doesn't
29+
* contain all statuses that the old workflow has. Status mappings can be provided by a combination of
30+
* `statusMappingsByWorkflows` and `statusMappingsByIssueTypeOverride`.
31+
*/
32+
statusMappingsByWorkflows?: MappingsByWorkflow[];
33+
version: DocumentVersion;
34+
/** Mappings from workflows to issue types. */
35+
workflowsForIssueTypes?: WorkflowSchemeAssociation[];
36+
}
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
import { JiraExpressionEvaluateRequestBean } from '../models';
2+
3+
export interface EvaluateJSISJiraExpression extends JiraExpressionEvaluateRequestBean {
4+
/**
5+
* Use [expand](#expansion) to include additional information in the response. This parameter accepts
6+
* `meta.complexity` that returns information about the expression complexity. For example, the number of expensive
7+
* operations used by the expression and how close the expression is to reaching the [complexity
8+
* limit](https://developer.atlassian.com/cloud/jira/platform/jira-expressions/#restrictions). Useful when designing
9+
* and debugging your expressions.
10+
*/
11+
expand?: string;
12+
}

0 commit comments

Comments
 (0)