Is it impossible to add issue templates with pre-populated text fields in Company Owned Projects?

[Madeline Bennett]

This feels like a dumb question. 

In Team Managed projects, you can pre-populate paragraph fields in the template builder so that when you create a new issue it already has rich text in it that users can fill out accordingly. 

However, Company managed projects do not seem to have a way to build out a template like that. Why is this? Is there a way to have pre-populated rich text in an issue template in a company-managed project?  

Worse comes to worst: If my team migrates to a team-managed board what will be the pitfalls? 

[Trudy Claspill]

Hello @Madeline Bennett 

Welcome to the community.

How are you accessing that template builder in your Team Managed projects? I'm not finding a feature like that in my Jira Cloud Standard environment. I wonder if that is present in your environment due to a third party app.

[Madeline Bennett]

No third-party app as far as I am aware. When you go into the issue types in the project setting section you can select the different fields you want to add via a menu on the right side of the screen. (Fields). 

There is a paragraph option that is rich text compatible. I added the paragraph option to my form. 

You can then type your pre-filled template copy into the default text section of the paragraph field. When you save changes your template is updated. When ever you create a new issue via the create button all of the paragraphs are pre-filled with the default text. 



I have included a screen shot of my view below

[Trudy Claspill]

Well, I learned something new! :)

But I don't work with Team Managed projects often. I administer the Company Managed projects.

With Company Managed projects, configurations are shared between projects, so intervention by a Jira Administrator is required to make customizations for individual projects.

Regarding adding default text to paragraph fields in Company Managed projects, for custom fields you can add default text by defining a Context for the field. A Context allows you to set a default value for a field and apply that to a specified collection of issue types and projects that use that field. it is not possible to add default text directly to the built-in field Description. There are work arounds for that, if you're interested.

There is significant impact to migrating from Company Managed project to Team Managed and vice versa. Here is a page that talks about that migration:
https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

There are additional impacts that are not spelled out in that document, and depend on what you have done to customize your Company Managed projects and how you leverage those projects.

[Trudy Claspill]

For a full description of the work around mentioned by @Mohamed Adel for templating the Description field refer to this post:

https://community.atlassian.com/t5/Jira-questions/Default-text-for-Description-field-on-Jira-Cloud/qaq-p/785597

[Mohamed Adel]

Thanks @Trudy Claspill  that's exactly the workaround 

[Mohamed Adel]

Hi @Madeline Bennett  , 

It is possible with a trick ,  you will need to create a new custom field call it "DescriptionX" that has a default value in it. And then with automation rule you will copy the value from the DescriptionX to Description and hide the field in view/edit screen 

there is copy value from another field on create issue event post-function but it has a bug and doesn't work properly , so it is better to use automation rule for that 

Regards

Mohamed Adel