Using a Jira Project to Implement Atlassian Tools, Products, Add-Ons, etc.

[Angela Stephens]

Hey Community!

I certainly cannot be the only one who uses Jira as my project tracking when implementing new Atlassian Tools, Products, Add-Ons, etc.

If this is something you've done, what is your approach? Do you have a standard template you upload into the new instance that contains all your Epics/Tasks, etc?

Thanks in advance for sharing your knowledge, and experience.

[John Funk]

Great - thanks for the info and sorry for the delay in responding.

There is an automation rule trigger now for Project Created. I would name your projects so that they start with certain words or letters, then you can add a condition so only new projects that start with that name will kick off the process. 

Then add more actions for Create issue and continue with one for each of your deliverables. 

[Angela Stephens]

Thanks John!  What I am working on is loading a set of deliverables and associated issues of various types into a Project called ~ Jira Admin & Support which is a step by step template for implementing Jira or JSM deliverables such as:

- New Kanban Project

- New Scrum Project 

- New JSM Portal/Help Desk

[John Funk]

Hi Angela,

We mainly use Automation for Jira create any recurring tasks. You could consider that to be a template if you like. I can give you some more ideas if you can provide some more details in what you wanting to happen when. 

[Jacob Vu]

Hi @Angela Stephens

Are you asking about using Jira natively as a project management tool?