Do any community members use a separate issue type to track actions in a project? i.e. "Action"

[jerry_raterman]

I am running projects for my customer where we agree on actions by engineers that need to occur before our next meeting.  Tried tracking these via email, Confluence, even SharePoint and Loop.  Most all my engineers prioritise their development work using Jira Epic, Story, Task tickets.  Does anyone have experience in creating an "Action" Jira Issue Type to ensure that an engineer has 1 queue for all in progress work?

[Vishal Biyani]

@jerry_raterman 

JIRA is flexible and organizations create issuetypes, issue hierarchies based on your business need.

You could very well create Action issuetype, create a JQL based on that issuetype and then probably create a kanban board for your team to visualize and prioritize the work.

Are there any specific concerns that you want to be addressed?

[jerry_raterman]

I would like to pilot the creation of an Action issue type.  I believe that there is a schema that needs to be created for each issue type.  How can I pilot the use of this?