JIRAInstance

Properties

Name	Type	Description	Notes
id	int		[optional] [readonly]
configuration_name	str	Enter a name to give to this configuration	[optional]
url	str	For more information how to configure Jira, read the DefectDojo documentation.	[optional]
username	str	Username or Email Address, see DefectDojo documentation for more information.	[optional]
default_issue_type	str	You can define extra issue types in settings.py * `Task` - Task * `Story` - Story * `Epic` - Epic * `Spike` - Spike * `Bug` - Bug * `Security` - Security	[optional]
issue_template_dir	str	Choose the folder containing the Django templates used to render the JIRA issue description. These are stored in dojo/templates/issue-trackers. Leave empty to use the default jira_full templates.	[optional]
epic_name_id	int	To obtain the 'Epic name id' visit https://<YOUR JIRA URL>/rest/api/2/field and search for Epic Name. Copy the number out of cf[number] and paste it here.	[optional]
open_status_key	int	Transition ID to Re-Open JIRA issues, visit https://<YOUR JIRA URL>/rest/api/latest/issue/<ANY VALID ISSUE KEY>/transitions?expand=transitions.fields to find the ID for your JIRA instance	[optional]
close_status_key	int	Transition ID to Close JIRA issues, visit https://<YOUR JIRA URL>/rest/api/latest/issue/<ANY VALID ISSUE KEY>/transitions?expand=transitions.fields to find the ID for your JIRA instance	[optional]
info_mapping_severity	str	Maps to the 'Priority' field in Jira. For example: Info	[optional]
low_mapping_severity	str	Maps to the 'Priority' field in Jira. For example: Low	[optional]
medium_mapping_severity	str	Maps to the 'Priority' field in Jira. For example: Medium	[optional]
high_mapping_severity	str	Maps to the 'Priority' field in Jira. For example: High	[optional]
critical_mapping_severity	str	Maps to the 'Priority' field in Jira. For example: Critical	[optional]
finding_text	str	Additional text that will be added to the finding in Jira. For example including how the finding was created or who to contact for more information.	[optional]
accepted_mapping_resolution	str	JIRA issues that are closed in JIRA with one of these resolutions will result in the Finding becoming Risk Accepted in Defect Dojo. JIRA issues that are closed in JIRA with one of these resolutions will result in the Finding becoming Risk Accepted in Defect Dojo. The expiration time for this Risk Acceptance will be determined by the \"Risk acceptance form default days\" in \"System Settings\". This mapping is not used when Findings are pushed to JIRA. In that case the Risk Accepted Findings are closed in JIRA and JIRA sets the default resolution.	[optional]
false_positive_mapping_resolution	str	JIRA issues that are closed in JIRA with one of these resolutions will result in the Finding being marked as False Positive Defect Dojo. This mapping is not used when Findings are pushed to JIRA. In that case the Finding is closed in JIRA and JIRA sets the default resolution.	[optional]
global_jira_sla_notification	bool	This setting can be overidden at the Product level	[optional]
finding_jira_sync	bool	If enabled, this will sync changes to a Finding automatically to JIRA	[optional]

Example

from defectdojo_api_generated.models.jira_instance import JIRAInstance

# TODO update the JSON string below
json = "{}"
# create an instance of JIRAInstance from a JSON string
jira_instance_instance = JIRAInstance.from_json(json)
# print the JSON string representation of the object
print(JIRAInstance.to_json())

# convert the object into a dict
jira_instance_dict = jira_instance_instance.to_dict()
# create an instance of JIRAInstance from a dict
jira_instance_from_dict = JIRAInstance.from_dict(jira_instance_dict)

[Back to Model list] [Back to API list] [Back to README]