Create Button on Jira

[Jagriti]

hi all

There is a create button on jira which can be used to create new issues.

I want to restrict the type of issues which users can create by clicking this button.

currently you can create Epics, Tasks ,Stories and Incidents ,directly by clicking the button.

I want to restrict this to only allow creation of Epics .( I do not want users to create tasks/stories without epics, so they must create an epic and then add issues in it )

thanks 

[Payne]

If you have the ScriptRunner add-on installed, this may be accomplished by using a Behaviour.

https://www.adaptavist.com/blog/restricting-issue-types-with-scriptrunner-for-jira/ 

[Jagriti]

thanks i do not know how to use Behaviors , pretty new to this 

[Nic Brough -Adaptavist-]

That's not how the create button process works.  Creating an issue allows you to select the project and issue type within it.  To do what you are suggesting means rewriting every segment of code that leads to a "create issue" process, and makes your user's experience of using the tool a bit of a nightmare (especially those who have used it before - you're going to get massive complaints as to why you've crippled it)

Take a more cajoling/persuading and vastly less coding route - create a validator for stories that checks that there is an Epic Link when creating stories.  Then they will have to put something in to it, linking stories to epics, they won't lose data when trying to create, and you only need one line of logic (more lines of code possibly, depending on what apps you have)

[Jagriti]

Hi Nic

I completely agree with you .

With "Validator" the scenario which I am  trying to avoid is , where users will select any random epic link from the drop down options available. Discipline around data sanity is a concern in my team .

[Nic Brough -Adaptavist-]

I'm afraid I can't recommend hacking the kernel of Jira in such a way, there's so much you will have to rewrite, it's not just the odd tweak here and there.

If you want to avoid "random click because validator", then the best route would be to report and shout.  Regularly search for "story with no epic link" and shout at/shame/punish the people doing it.  One trick might be "your timesheets are not complete until every story has an Epic".  Or, ideally, don't force them to do stuff they don't want to!

I forgot earlier.  The desire "every story is part of an epic" often, but not always, suggests that your epics are probably projects and/or items that should belong to dedicated teams.  Epics are usually collections of strongly related stories leading to a goal, but it is perfectly normal to have swathes of stories that do not fit that description, placed into projects appropriately.

[Jagriti]

Thanks Nic  for your valuable feedback .

I have just tried using Validator for Epic Link ( this rule now applies to story and subtasks)

Also i have added post functions to :

-inherit epic link to story from epic  (works fine)

-inherit epic link from story to sub-task (doesn't work)

there is an error message on sub task screen now: "A subtask cannot be assigned to an epic."

Please advise .

Thanks