Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Create Sub-task on transition (Bob Swift) not working for some users.


Hi Community,

we are using the Bob Swift Create Sub-task on transition for some projects and it was working perfectly fine until some days ago. 

Some user are reporting when clicking on the transition button the subtask are not created. Its weird because when i click the button it works fine. The user had no problem in the past and have all the permissions. Even when i change to that user on my system i can create the subtask via the button on transition. 

The problem occurs only in one project and in one specific issuetype as far as we know. 

Thank you and cheers!

EDIT: i could pinpoint the problem to the second Node. Some post-functions scripts threw errors since they could not find specific customfields on this node. So issues edited on this node are unable to generate subtasks. 

EDIT2: So Node2 can not find (some) customfields by name in scripts and bob-swift- create-subtask. I use something like "%parent_cFName%" or in Scripts ...getCustomFieldObjectByName("cFName"). These dont work anymore.
When i use the ID instead like "%partent_customfield_ID%" then it works! A workaround but not really the solution.
So it seems like a indexing Problem. I will start a new index process.

1 answer

1 accepted

0 votes
Answer accepted

The second Node could not finde some CustomFields by Name only by ID. After a new index process everything works fine!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events