LogoLogo
👉 Get a free ITSM ebook
Issue Templates Agent
Issue Templates Agent
  • Introduction
    • About Issue Templates Agent for Jira
      • Main features of Issue Templates Agent
      • Key benefits of using Issue Templates Agent for Jira
    • Template examples
      • User story template
      • Bug report template
      • Test plan template
      • New employee onboarding template
      • Employee offboarding template
      • Helpdesk template
      • Purchase Request Template
    • 📚 Glossary
  • Using app
    • Get started - app configuration 🚀
    • Create template
      • Create a simple structure with subtasks
      • Create an advanced structure with subtasks
    • Use a template to create issues
      • Use issue templates from issue view
    • Usage in Automation
      • Apply Template on existing issue
      • Create Issues with structure from Template
      • Create new projects with issues
      • Schedule issue creation
    • Manage templates
    • Permissions
    • Draft issue templates
    • Variables
    • Supported fields
    • ⭐️ Best issue templates practises
  • 💬FAQ
  • Featured articles
  • Known limitations
  • Security statement
  • 🤝Support
    • Book a free demo 📅
    • Request a bug 🐞
    • Share your ideas 💡
  • For Solutions Partners
    • Partner Portal
    • Our Partners 🫶
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page
  • Issue Templates Agent Architecture
  • Useful links and more information

Was this helpful?

Export as PDF

Security statement

Information below applies to the Issue Templates Agent for Jira cloud app.

PreviousKnown limitations

Last updated 9 months ago

Was this helpful?

We are committed to improving our security posture. That’s why we created this page to answer basic questions about security in the Issue Templates Agent app.

Since Oct 2023, we've been SOC2 type II compliant to meet the highest and most professional standards.

SOC 2 report is available for all our customers at any time at our .

Issue Templates Agent Architecture

is built on the platform. The app connects to Jira using . It’s written in React and TypeScript.

What customer data does the app process?

We process accountIds, email addresses, display name.

What data does the app store?

The app stores templates data.

Where are the data stored?

All data are stored on the Atlassian infrastructure. Templates data is stored in Jira (). The app configuration is stored via .

What permission does the app require?

Permission

Usage

Endpoint(s) in methods

manage:jira-configuration

Creating Template custom field if field doesn’t exist (done in upgrade tasks).

Creating a custom field context. Used when options are updated for template.

Getting mappings for a field in issue for particular project. Used when applying UI modification for the following field types: single select, multi select, checkboxes.

Getting custom field context for a project. Used when updating options for a template and during template deletion.

Getting custom field option for a context. Used when creating a custom field context and during template deletion.

Creating options for a custom field. Done during template creation and update.

Updating options for a custom field. Done during template update.

Deleting a custom field option. Done during template deletion.

Getting issue type screen schemes for projects. Done during adding Template field to create screens.

Getting issue type screen scheme items. Done during adding Template field to create screens.

Getting contexts for a custom field. Used for example when getting predefined options for the select field type.

Getting values for the priority field.

manage:jira-project

Adding template field to create screens for particular projects. This process involves getting list of screen schemes, tabs for a screen, fields for a tab, adding a field to a screen tab and moving a screen tab field.

storage:app

Saving plugin related data in the Storage. For example, custom field config is saved in the Storage and this data is used on create issue screen when reading what kind of fields are supported by our app for UI modifications. Another example is that we save templates names in the Storage so when someone is creating or updating a template we can verify if such template already exists.

read:jira-work

Getting a custom field option. Done during template update and deletion.

Getting UI modifications to display in the table.

Updating UI modifications when template is updated.

Creating UI modifications when template is created.

Getting supported fields to display in the field selector while creating/updating template.

Getting the JQL search auto complete suggestions for the labels field.

Getting components for a project.

Getting versions for a project.

read:jira-user

Getting a user for a user picker field.

Getting users for a user picker field for handling multi selection.

Getting users for a user picker field with specific search conditions.

write:jira-work

Required for loading and applying UI modifications on the create issue screen.

Does the app encode all data in transit and at rest?

Yes.

Does the app support data residency?

Does the app have a data retention policy?

Does the app have a data backup policy?

Useful links and more information

g

Yes, thanks to using the Atlassian Forge platform. Here is the official announcement from Atlassian:

Yes. Upon written request, Appsvio and Atlassian will delete all End User Personal Data (including copies). More information is available in .

Yes. More information is available in

If you have any questions about the security, e-mail .

Trust Center
Issue Templates Agent
Forge
OAuth2
via UIM entities
Forge Storage
https://www.atlassian.com/blog/developer/data-residency-is-coming-soon-in-beta-to-forge-hosted-storage-take-action-now-to-support-your-customers
Forge DPA
https://www.atlassian.com/trust/security/data-management
Appsvio Trust Center
Privacy Policy of Appsvio apps
security@appsvio.com
createCustomField
createCustomFieldContext
getCustomFieldContextsForProjectAndIssueType
getCustomFieldContextForProject
getCustomFieldOptions
createCustomFieldOptions
updateCustomFieldOptions
deleteCustomFieldOption
getIssueTypeScreenSchemaForProjectIds
getIssueTypeScreenSchemaMapping
getCustomFieldContexts
searchPriorities
etScreenSchema
getScreenTabs
getAllTabFields
addFieldToTheTab
moveFieldToPosition
getCustomFieldOptions
getUiModifications
updateUiModification
createUiModification
getFields
getFieldAutocompleteSuggestion
getProjectComponents
getProjectVersions
getUser
bulkGetUsers
findUsersForPicker