Interface MutableIssue

Facade for an issue's GenericValue. After calling any 'setter' method, you will need to call store()
to persist the change to the database. Note that this is a 'shallow' store - only fields directly part of the issue
(in the database schema) are persisted.

setParentObject

Normally a subtask just has the ID of the parent set
using setParentId(). In this case, the getParentObject() method will look up the parent object from
the DB (or cache). However, when you are editing a parent and its subtask within a transaction (eg a Bulk Move),
it is useful to be able to link the subtask to the pending parent object in order that it can see the
new values for the parent.