Is it possible to create a rule to create subtasks for multiple stories that already exist?

[Hussain Ali]

I have over multiple stories (over 20) in the backlog and I need to create subtasks for all of them. All subtasks will be the same and so will their descriptions. 

I have already created a rule where any NEW story that gets created will have these subtasks but I am not sure what type of "trigger" I can use to create subtasks for all these stories in the backlog that already exist. 

Trying to avoid spending time going into each story (that already exists) and creating 4 subtasks with their specific descriptions - 

Any ideas?

[Sateesh Chandra]

Please hide them in the Field configuration scheme of the project and particular issuetype. The fields will actually be present on the screen but will not be visible to the users. Make sure you do not mark them as mandatory.

[Nic Brough -Adaptavist-]

Remember that this completely hides your fields for the issue type. You won't be able to edit them later in the lifecycle of the issue.

[Sateesh Chandra]

Yes, you will need to unhide to make the changes if any.

[Nic Brough -Adaptavist-]

You can't just hide and unhide things in a field configuration scheme - you have to be an admin.

[Nic Brough -Adaptavist-]

The default is to show all available fields so that the users are aware that they are there.

They can hide them later in their preferences, but if you don't want the fields on the create screen at all, just remove them.