Is there a way to refresh story points on subtasks that move parent tickets?

[Meghan McPolin]

I have story points on subtasks that automatically refresh totally up to the parent ticket.

If I move a subtask, the story points do not deduct from the old parent and do not update the new parent ticket's story points. Is there a way to automatically refresh the story points?

Background: We are trying to count story points for bugs in each sprint. We want a task to have 40 story points a sprint. Every time a new bug is raised, we want to move the subtask to a new bug and count the points on that bug. This way, the story points should deduct from the tasks and we are not adding more story points to the sprint.

Example:

Original Story Points Summed Up from Subtasks:

1. Parent #1 = 3 story points
   1. Subtask 1- 1 story point
   2. Subtask 2- 1 story point
   3. Subtask 3- 1 story point
2. Parent #2 = 0 story points (no subtask)

----- Move subtask (More --> Move --> update new parent ticket #)

Actual Result: 

1. Parent #1 = 3 story points
   1. Subtask 1- 1 story point
   2. Subtask 2- 1 story point (moved the Parent #2)
   3. Subtask 3- 1 story point
2. Parent #2 = 0 story points (no subtask)
   1. Subtask 2- 1 story point

Expected Result:

1. Parent #1 = 2 story points
   1. Subtask 1- 1 story point
   2. Subtask 2- 1 story point (moved the Parent #2)
   3. Subtask 3- 1 story point
2. Parent #2 = 1 story point (no subtask)
   1. Subtask 2- 1 story point

[Nic Brough -Adaptavist-]

No.  The Connect framework for add-ons is not going to be implemented on server, and the ability to add server add-ons to Cloud is limited (you can only add the handful Atlassian have chosen, and they are shrinking the list, not extending it)