As a special case, self-assignment is refered to as claiming assignment
of an issue.  The assignee list on the issue sidebar will now properly
identify users which have assigned themselves, and the issue event log
will now contain "Bob claimed" instead of "Bob assigned Bob" when such
an event occurs in the future.

Signed-off-by: Malfurious <m@lfurio.us>

Active issue assignees will now have a button on issues to explicitly
'signoff' their assignment - that is, to affirmatively declare it done.
The use of this new action will allow assignees to signoff without
needing to close the issue as well.  This is useful for multiple
assigned users collaborating on an issue.

Note that if an assignee chooses to close a ticket directly, they are
still automatically signed-off, as before.

To aid this feature, the low-level definition of an 'assigned user' is
updated to exclude users occupying an assignment slot, but which have
already signed-off.

Since the icon representing this action is the same as for closing a
ticket, the buttons enabling these two actions are now color-coded
wherever they appear.

Signed-off-by: Malfurious <m@lfurio.us>

The previous patch removed the guid from the far left side of
issueListItem entries.  This patch makes that value visible again within
the popup issue modal window.

Additionally, the issue's current stage is displayed next to its name.
Viewing this info here is convenient, however this is mostly done in
anticipation of being able to access issues from the main user
dashboard, where pad stage context may be missing.

Signed-off-by: Malfurious <m@lfurio.us>

Previously, issues on pads owned by a group (rather than by a user)
would incorrectly present options for user assignment.  It would show
the group as a member of the list, misleadingly with the user icon to
the left of it.

This patch uses the new agent::getContainedUsers() function to resolve
the pad's owner to an array of users accessible via the owner 'agent'.

Signed-off-by: Malf Furious <m@lfurio.us>

Disallow posting to closed issues.  This is a temporary soultion and
will likely be reverted in the future.  The main reason this is being
done now is because this form, as written, depends on an open issue
state.

To aid diff comprehension, note that most lines are only indented one
level, the code area affected is wrapped in a PHP if.

Note that form submissions are still allowed for closed issues.  This
commit only disable the _displaying_ of the form.

Signed-off-by: Malf Furious <m@lfurio.us>

This allows users to add assignees when posting to an issue.  A dropdown
is revealed which contains the pad owner and all members.

Signed-off-by: Malf Furious <m@lfurio.us>

If this submit button is used, the message will be posted as usual, then
the issue will be moved to the next stage in the pipeline.

Signed-off-by: Malf Furious <m@lfurio.us>

I'm going to be adding another button down here in the btn-group (more
later).  So to make room, I'm removing the text on these buttons,
leaving only the icons.  The text will instead be a tooltip, visible
when the button is hovered.

In the case of the 'Close issue' button, it is changed from btn-success
to btn-default.  I will tweak colors once this portion of the UI
matures.  For now, I don't want the rainbow in my face.

Signed-off-by: Malf Furious <m@lfurio.us>

Signed-off-by: Malf Furious <m@lfurio.us>

Since this form submits a file upload, we need it to be set
enctype="multipart/form-data".

Signed-off-by: Malf Furious <m@lfurio.us>