Skip to main content
JamesM-MERGE
JamesM-MERGE
Level 4
July 25, 2023
Solved

Text Mode Help: Project Report Group by Issue / Request Name

I am trying to determine if it is possible with Text Mode to group a Project report by the Issue / Request Name.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Madalyn_Destafney
Madalyn_DestafneyAccepted solution
Community Advisor
July 25, 2023

It may be easier to have an issue report grouped by resolving object (project)…would that work for your situation? Or even if not grouped by resolving project, could have that as a column in the report.

If this helped you, please mark correct to help others : )
View in thread

9 replies

JamesM-MERGE
JamesM-MERGEAuthor
Level 4
July 25, 2023

I tried grouping by Converted Issue Originator >> Name, and switched that to Text Mode which resulted in:

textmode=true
group.0.linkedname=convertedOpTaskOriginator
group.0.namekey=view.relatedcolumn
group.0.valuefield=convertedOpTaskOriginator:name
group.0.namekeyargkey.0=convertedOpTaskOriginator
group.0.namekeyargkey.1=name
group.0.valueformat=string

Then I changed it to use the Issue Name:

textmode=true
group.0.namekeyargkey.0=convertedOpTask
group.0.namekeyargkey.1=name
group.0.valuefield=convertedOpTask:name
group.0.valueformat=string
group.0.namekey=view.relatedcolumn
group.0.linkedname=convertedOpTask

 

This seems to work. However, many projects listed on the report are grouped under a "No Value" grouping even though they have a resolved Issue / Request.

Translate
NicholeVargas
Adobe Employee
NicholeVargasAdobe Employee
Adobe Employee
August 3, 2023

@jamesm-merge I used your exact text mode above in my personal Workfront instance and the same behavior occurred. The ability to report on the converted issue is relatively new functionality (prior to that field creation, you had to create a calculated custom field), and I realized that projects in my instance dating back to 2020 were the ones that weren't populating and instead were falling under "No Value." Is that the same behavior you are seeing? 

If that is the case, I don't believe there is a way to retroactively populate historical data. I tried creating a calculated field for {convertedOpTaskName} and attaching that to the project / recalculating the expression, but since the project has already been converted, it didn't pull in. 

If the behavior you are seeing dates back to 2020/2021 and you think this is the root cause, let me know and I can follow up with Workfront Product to see if there is a way around that, or a way to populate past data that I'm unaware of. 

Translate
JamesM-MERGE
JamesM-MERGEAuthor
Level 4
August 9, 2023

In my case the projects under the No Value all have an Entry Date of this year.

Translate
Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity AdvisorAccepted solution
Community Advisor
July 25, 2023

It may be easier to have an issue report grouped by resolving object (project)…would that work for your situation? Or even if not grouped by resolving project, could have that as a column in the report.

Translate
If this helped you, please mark correct to help others : )
JamesM-MERGE
JamesM-MERGEAuthor
Level 4
July 26, 2023

Thanks, I'll try that.

Translate
Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity Advisor
Community Advisor
August 30, 2023

How did that work out for you?

Translate
If this helped you, please mark correct to help others : )
Terms & ConditionsAccessibility statement

Loading footer...