Skip to main content
BrandonNW
Level 6
Jun 16, 2021 8:39 PM UTC
Question

Keeping the converted issue "tied" to the resolving project

This should be an easy one. I am either missing something obvious or this isn't possible. I have a scenario that is searching for new requests/issues from a certain queue and converting them to a new project when they submit the request. When this runs, it pulls over the converted issue data (entered by, entry date, etc...), but then it deletes the converted issue. I am using a WF Misc Action card with an action of "convertToProject" and I have "Has Resolvables" checked. I can't think of another way to do this. Is there an option I am missing to keep the issue and tie it to the resolving object?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

6 replies

Level 3
Jun 16, 2021 8:46 PM UTC

Hi Brandon,

At the bottom of the Misc Action module, there is an attribute called "options". Update that with "preserveIssue".

That should solve your concern

Translate
BrandonNW
BrandonNWAuthor
Level 6
Jun 16, 2021 10:33 PM UTC

Boom! I was literally staring at that field the whole day today because I knew it had to be in the options somewhere. I may have one more question on how to change the project to a custom status, but I will play with it a bit first before I bug this group again. 😋

Translate
BrandonNW
BrandonNWAuthor
Level 6
Jun 16, 2021 10:42 PM UTC

oh - I just realized it removes the converted issue from the submitted screen though. It removes it because the automation auto-closes the issue. I need the issue to mirror the project custom status. Is there another option trick that can do that?

Translate