I have built 3 different data capture screens for the same project.......how do i determine what screen needs to be used based on the status of a ticket, and who is entering the data
Hello @Rob Baulman
Welcome to the community.
Can you provide more information about your scenario?
Are you working with a Jira Software project? It will say at the top of the navigation pane on the left.
Are you working the a Company Managed project or a Team Managed project? That will be at the bottom of the navigation pane on the left.
Are you talking about screens for the initial creation of an issue? Or for changing an issue from one status to another later in the workflow?
Can you provide more information about the specific scenarios where you see each of these screens being needed?
Thanks @Trudy Claspill ,
Yes it is Jira Software project, and it is a company managed project.
I need to have a single project so i can manage the work in a single stream...as we are a profit centre for the business
The work comes to us from 3 different internal teams.... and each team has different information relevant to them.....
I wanted to create a specialised issue creation screen for each of the 3 internal businesses for simplicity to the user.
From there, my team will use a Master screen with all relevant tabs, and thats working beautifully
Hello @Rob Baulman
Your post has been tagged that you are using the Free version of Jira. Are you truly using the Free version or are you on a paid subscription?
I ask because with the Free subscription you can have only up to 10 users, and your scenario sounds like you will need to grant licenses to more than 10 users. Each of the individuals that need to create issues from those 3 internal businesses will also need to be a licensed user in order to create issues in a Company Managed Software project.
For Software projects Jira does not have a native method to allow you to present different Create Issue screens to different users for a single issue type within the Jira UI. You might be able to find that functionality by leveraging a third party app. I have not needed such functionality before, so I don't have any recommendations.
You might also look at using Jira Service Management as the work intake tool. With that product your internal businesses could submit requests without consuming user licenses. You could create intake forms customized to the internal businesses. You could use automation to create Software issues based on the creation of those Service Management issues. Your internal business users would not be able to interact directly with the issues in the Software project, but you could use additional automation to synchronize information between the Software issues and the Service Management issues to keep you internal business customers informed.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...