There's four ways to copy values into "comment" that I can think of:
However, I'm not sure it's actually useful to copy values into comments. Comments are for having a conversation about the issue, I can't think of a reason to spam it with bits of data that's already in the issue. Could you explain the actual reason for wanting to do this? There may be better approaches than duplicating fields into comments.
Thanks for the quick response. We have project in that planning notes is a CF and every two weeks Assingee will update his work. After the PL Lead will take report based on that. Now PL wants to transfer that after his report to Comments.
Instead of keeping update in Comments he wants to keep in Planning Notes first then he wants to move that.
HOpe I have given enough background.
Now He don't want that on Workflow transition. With this Post function went off. Rest three are the solutions.
Now, can you please guide accordingly?
I think your user needs to decide whether the field is of any use - they should be doing the planning notes in the field or the comments. Not both.
Still, if you must do it, the best option is a listener that can pick up any changes to the issue, decide when to duplicate the data and spam the comment with it.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs