I have a scenario where I am automatically approving an issue and updating its status to Approved. After the approval, I attempt to convert the issue into a project using the Misc Action module. While doing this, I select the Preserve Issue option so that the original issue remains and is linked as the resolvable object for the newly created project.
However, once the conversion happens, the issue’s status changes to New because the project begins in the Planning status. My intent is to retain the issue’s status as Approved, even though the project itself starts in Planning.
Is it possible to maintain the issue’s status as Approved in this scenario?
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
I am not a fusion expert so module wise someone else might have an idea. But I look at your situation from a process perspective. Have you considered changing the process steps. Convert your issue to a project and then approve the issue? You might consider a router so that Fusion approves your issue and finishes the set up of your project. Just a thought when read your scenario.
Thank you for your reply @ScottMo1 Yes I tried the same way also as you are telling i.e.
Say first autoapprove the issue then convert the issue to project successfully post which the issue status again get changed to New since project status is planning. Then again I had try to change the issue status to approved but got the below error which I think is expected.
The following error occurred: You cannot change the status of this issue manually because it is linked to the project "PROJECT-Ads & Campaign 19". Each change in the project status also changes the issue status
So I guess it wont work in that way.
Views
Replies
Total Likes
Hi @sumitshp,
This is expected behavior https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-26961#:~:text=If%20you....
It happens because
"If you’re using Adobe Workfront and can’t change the status of an issue, it’s likely because the issue is linked to a project. In this case, the project controls the status. To fix it, you need to remove the project relationship from the issue."
If you want to resolve this and make it work as you intended you have to remove the relation, but they you lose ability that the issue status is automatically resolved once project is finished. Hopefully this makes sense.
Best regards,
Ivan
Thank you @IvanBebek-iX for your kind reply. I understand it is a expected behavior. The way around is unlinking the issue from the project as you said which I had initially tried. But If I unlink it then there might be some concerns in for the workfront team to create a report for the number of issues that are being converted to project.
@sumitds Just checking in. Were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could benefit the community. Thanks again for being part of the conversation!
Views
Replies
Total Likes