|
I am not hoping that they are automatically done, but I can make a custom workflow screen that have these fields. If the workflow screen has the fields and buttons (much like I can do with Attach File), I don't see the issue. If you are using <div> tags for these "groups" of fields, you should be able to stick them on any screen anywhere and still function fine. Sorry i didn't find JRA-6747 on my earlier search and thanks for linking them. I voted for it.
Tom,
I can definitely see the need for the ability to Move and Clone issues. However, I cannot see why these operations need to occur as part of a workflow. Is the need to only allow the Move or Clone operations when an issue reaches a particulare status? As I have mentioned, the Move operation is a wizard, which potentially migrates an issue from one workflow to another. It will not be possible to move an issue to another workflow while an issue is transitioning through the current worklow. Cloning an issue creates a completely new issue. The operations mentioned in JRA-6747 are all related to the issue that is being changed. For example, creating a link for the issue that is currently being changed, or logging work for the issue that is being changed. It would be a lot more difficult to make the clone operation fit into this architecture. Due to the number of new feature requests and their popularity, unfortunately, I do not think we will be able to look at making these improvements soon. However, I would really appreciate, if you could provide more explanation as to why you would like to perform Move and Clone as part of the actual workflow, rather than as standalone operations, that could be used when needed. I am very interested in your usecase. Cheers, Once the support call is at tier 3, it is either resolved or confirmed as a bug. If a bug, then it needs to be cloned/moved to the proper programming project and then linked back to the Help Desk ticket.
General Workflow Tier 1 (initial call or review of help desk request) => Resolved Tier 1 is Customer Service, Tier 2 are product experts with a reasonable amount of technical background, Tier 3 is the development group. Tier 2 working with Tier 3 can agree that it is a bug or what ever the case may be, then it needs to move to one of our development projects so it can be cued up and tracked. Tom,
Thanks for the update. It will be quite challenging to make the clone & move happen as part of workflow. To add to the comments above, another place where making clone/move occur as part of workflow will be very difficult, is if a Bulk Transition is executed. As in this case, we would need to make Bulk Clone and Bulk Move occur, which will be very confusing. The best way to approach this would be to instruct Tier 3 support to clone and move the issue once it has reached the specific status using the already existing operations. If the process of clone and move needs to be triggered automatically, another way to go is to customise JIRA such that when the issue reaches a certain status, redirect the user's web browser to the beginning of the clone operation. If you are interested you can have a look at customising JIRA in house. Alternatively, you may involve one of Atlassian partners who specialise in extending JIRA. If so, please send an e-mail to: Also, please note that if you do this, you may want to remove the Bulk Change permission: Please note that the customisation will need to be ported every time JIRA is upgraded. Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Critical
Allow WorkFlow transistion Screen to take advantage of Operation screens.
Converting operations such as Link Issue and Log Work to fields is tracked via JRA-6747. Please vote for JRA-6747, if you have not done so already, and add yourself as a watcher to that issue to receive updates on its progress.
While we would love to implement all great enhancements to JIRA, we have to do them one at a time. These enhancements are not part of
JRA-7661as the effort to convert issue operations to fields is very different from the work to allow users to edit active workflows.For more information on how new feature and imporvement requests are scheduled please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements
Ability to move issues as part of worklfow is tracked using
JRA-9564. However, I am not sure if we will be able to get this one done. The reason is that Clone Issue and Move Issue are wizard operations, that have nothing to do with transitioning through workflow. As they are wizards, it is not possible to convert them into Issue Fields, like Add Attachment or Link Issue, and therefore I am not sure how we can make them happen as part of workflow transition.As the enhancements are tracked using other issues I will resolve this issue. Please let us know if you have any other questions or would like more information by adding a comment here.
Cheers,
Anton