Issue Details (XML | Word | Printable)

Key: JRA-7381
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Ann-Sophie HOCQ
Votes: 3
Watchers: 4
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Create new operations

Created: 19/Jul/05 02:35 AM   Updated: 05/Mar/08 03:27 AM
Component/s: Custom Fields, Issue navigator
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Ann-Sophie HOCQ, Dampsoft, Jeff Turner [Atlassian], Logan Johnson, Luke Davies and Scott Wolk
Since last comment: 39 weeks ago
Labels:


 Description  « Hide
We have new custom fields but these fields must be filled apart from an action of the workflow.
So it will be interesting to create operations to fill these custom fields.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Logan Johnson added a comment - 12/Aug/05 10:59 AM
I am adding a "release notes" custom field now. It would be very helpful if I could add an operation to "Add a release note to this issue".

Jeff Turner [Atlassian] added a comment - 15/Aug/05 09:13 PM
I'm not sure how a "Add release note" operation would differ from a "Add release note" workflow action available from every step?

Luke Davies added a comment - 15/Dec/05 11:18 AM
I would like to be able to have a custom field for an external e-mail and then have a custom operation to send an external e-mail. The e-mail would then be send from the project e-mail address as normal by the e-mail service. This e-mail would not only be sent but added as an action ( maybe as a comment with the e-mail body as the text ) to the issue history.
This would be very useful

Scott Wolk added a comment - 23/Jul/07 04:45 PM
I'd like to add an operation to easily change the fix in version

Dampsoft added a comment - 05/Mar/08 03:27 AM
We would uses this feature to assigne the person who should test the issue in a seperate custom field.
If we would use a workflow action, we would have to add this action to every single status of every workflow.
Since the target status is the same as the source status we can't use a common-action.
Having 8 possible states and 5 workflows it is too easy to miss some configurations.