How to restrict who can access the new create button

[Lex Baldridge]

Hello,

I have noticed Jira updated and with this there is now a new create button. I don't want people on m board to use the create button but the forms instead. I figured out how to remove the permission to the create button on the board. However, I am not sure how to restrict this one (shown below).

[Walter Buggenhout]

Hi @Lex Baldridge,

Hmm ... that create button has been there all the time. It is the central entry point in Jira to create work items. You can't hide it. People will only be able to create work items in the products they have permission to do this.

If your Jira instance is properly configured, then people will see the same fields to fill out as the ones you added to your form. So, apart from it looking a bit different, there's not too much that could go wrong there.

Hope this helps! 

[Trudy Claspill]

@Lex Baldridge 

Can you provide more information about why you want to direct users to the Form rather than using the native Create dialog that is available when the Create button is clicked?

Also, what type of project does this concern? Get that information from the View All Projects page under the Projects menu.

[Lex Baldridge]

This is a team managed business, we want to use the forms to keep a better back log of everything and this way people who are not on the board can submit forms also.

[Trudy Claspill]

How does using the Forms help you "keep a better backlog of everything"?

What do you mean by "people who are not on the board"? Are those people who are not assigned a role in the project? People who do not have licensed access to your Jira site?

What is the Access Level for your Team Managed project?

What is the Access Level for the Form?

[Koloman Pfeffer]

@Trudy Claspill and @Walter Buggenhout 

We are having the same issue or request right now, that we want to restrict usage of the create button, because it leaves too many freedoms to users who don't read what they are actually creating.

It is problematic, that work type and request type have a default value in there where people don't need to change it to create a work item. So forms just lower the chance for error.

Also on the create screen you can't use conditional logic as in (JSM)-forms, which is one of the biggest benefits of forms.

So there are many valid reasons why people would want to restrict access to work item creation via the create button. I find it a bit disappointing and frustrating, when the only answers to a question are trying to invalidate the issue a person has instead of explaining.

[Trudy Claspill]

Hello @Koloman Pfeffer 

I have to disagree with you that my responses invalidated the question the author asked. My responses only asked for additional information relevant to the use case so that I would be better informed when trying to provide a relevant and useful answer.

I welcome constructive and thoughtful feedback on how my responses could be interpreted as invalidating the original question, as doing so was not my intention.

With regard to your scenario, to provide a relevant response I would ask you similarly for more information.

You have mentioned that you can't use logic as in "(JSM)-forms". Is that an indication that your scenario involves a JSM (vs. Software or Business) project? And is that a Team Managed or Company Managed project?

The original author mentioned that their project is "team managed business". As such they would be using different forms functionality than what is available for a Jira Service Management project. If you scenario involves a JSM project, I encourage you to start a separate Question thread for that discussion. Otherwise this one thread could become confusing with responses relevant to one type of project but not the other.

There are more questions I would ask if the scenario concerns a JSM project, but I'll save those for the separate thread you start, if that is in fact your scenario.