Keeping the converted issue "tied" to the resolving project | Community
Skip to main content
BrandonNW
Level 6
June 16, 2021
Question

Keeping the converted issue "tied" to the resolving project

  • June 16, 2021
  • 1 reply
  • 1564 views

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.

1 reply

Level 3
June 16, 2021

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

Level 4
November 2, 2022

Hi, any idea if this function has been removed?  I have the following:

{
    
project: {
"name""Testing Sales Pursuit Plan",
"programID":"6361406b001ac75c4b6e185d8ab832b3",
"templateID":"63530b84000195201b931038d97f3c1b",
"plannedStartDate":"2022-11-01",
"options":"preserveIssue"
}
}
 
And it creates a project from the template, but it still deletes the issue, and none of the custom fields from the issue transfer to the project.  Where can you find a list of items you can put in the "options"?  Thank you!
undu82
Level 2
November 14, 2022

Hi, you need to use this structure:

 

{
    "options": [
        "preserveIssue",
        "preservePrimaryContact"
    ],
    "project": {
        "name""Some Name",
        "templateID""Some ID",
        "ownerID""Some Owner",
        "status""PLN"
    }
}