Colleagues, tell me, please, what are the best practices that can be applied to create a scenario:
1. There is an external user who should start tasks only of type "stories".
2. See only these tasks (of one type - "stories").
It's about access to one project.
Out of the box JIRA does not allow controlling what issue types user can create. There are some posts about using scripting to control that. By external I presume you mean they will not have a JIRA account. You would need to allow browse and create issue access to the project by 'anyone'. In my opinion, not really a good idea. You can use an issue security scheme to control access to the issues, If you can control what issues the user can create you can use an issue scheme that only allows the user to see issues they are the reporter for. Maybe someone else can help you with the 'anyone' access. I've never used it.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events