LogoLogo
👉 Get a free ITSM ebook
Issue Templates Agent
Issue Templates Agent
  • Introduction
    • Welcome to Issue Templates Agent!
    • Template Examples
      • User Story Template
      • Bug Report Template
      • Test Plan Template
      • Employee Onboarding Template
      • Employee Offboarding Template
      • Helpdesk Template
      • Purchase Request Template
    • Best Practices
    • Additional Materials
  • Features
    • Create Templates
      • Basic
      • Simple
      • Advanced
      • Scheduled
      • Save Templates as Drafts
      • Variables
      • Supported Fields
    • Templates on Create Issue View
    • Templates on Issue View
    • Automation and REST API
      • Apply Template on Existing Issue
      • Create Issues with Structure from Template
      • Create New Projects with Issues
      • Schedule Issue Creation
    • Tracking Templates Usage
    • Company vs Team Managed Projects
    • Bulk Edits
    • Template Library
    • Audit Log
    • Import and Export Templates
    • Permissions
  • Resources
    • Security Statement
    • FAQs
    • Related Articles
    • Release Notes
    • Contact our Support
Powered by GitBook

Security

  • Privacy Policy
  • Appsvio Trust Center

appsvio.com © 2025 All rights reserved

On this page
  • Team-managed projects:
  • Company-managed projects:

Was this helpful?

Export as PDF
  1. Features

Company vs Team Managed Projects

Are there any differences for templates in company or team-managed projects? Read along.

Issue Templates Agent currently supports both the company vs team-managed projects, where you can enjoy the benefits of using templates. However, there are some differences and limitations, when it comes to both project types.

Team-managed projects:

  • The template field in the Create Issue view needs to be added manually, as there's no API to do it automatically

  • The template structure can only be created for one project, the one you are currently in, as only these issue types will be available for use

  • For the parent field to be filled in properly from template, all of the issue types in the template need to be from one project, the one in use

  • For the import of templates - the structure of the template is already defined within the file, so only 1 project can be used and all of the issue types that belong to that project

Company-managed projects:

  • The template field is added automatically to the Create Issue view

  • The template structure can be created for multiple projects - you can use issue types from different projects

  • The parent field can be filled in from the template with multiple company-managed projects and issues

  • For the import of templates - the structure of the template is already defined within the file, and here you can use multiple projects just as issue types

PreviousTracking Templates UsageNextBulk Edits

Last updated 3 days ago

Was this helpful?