Report fields: Entered by, Submitted by, and Converted Issue Originator | Community
Skip to main content
R
R_Kephart
New Participant
March 1, 2023
Solved

Report fields: Entered by, Submitted by, and Converted Issue Originator

  • March 1, 2023
  • 3 replies
  • 2052 views

Hello Workfront Community,

I am working on 2 reports: one for projects and one for issues. I'd like both to filter on the user that created the issue. However, I have some items appearing on the Issue Report that do not appear on the project report. At this point I can probably move forward with only the Issue report and simply display project information, however my curiosity is now peaked. 

 

What is the difference between Entered by and Submitted by on issue reports? How do those fields relate to Converted Issue Originator in Project Reports? 

 

Thanks for your Time! 

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

WF's definition of Converted Issue Originator: A field in a project or task report that displays information about the user who is the Primary Contact of an issue when the issue is converted into a project or task. The field also displays in the Project Details section where it displays the name of the Primary Contact of the converted issue. 


And then related to above, Primary Contact:

The Primary Contact is the creator of an issue and it is automatically designated by Workfront when the someone creates the issue. You can manually update this field if you have Manage permissions to the issue. An issue can have only one Primary Contact. If you change the Primary Contact, the user originally designated as the primary contact still has Manage access to the issue. When converting an issue to a task or a project, the user designated as the Primary Contact of the becomes the Converted Issue Originator of the project or task. If the Primary Contact of the issue is updated after the issue was converted, the Converted Issue Originator will be preserved as the Primary Contact of the issue at the moment when the conversion happened.


Bookmark this useful WF terminology glossary! https://experienceleague.adobe.com/docs/workfront/using/basics/workfront-terminology-glossary.html?lang=en

If you found this useful, please mark correct to help others : )

 

3 replies

Lyndsy-Denk
Lyndsy-Denk
New Participant
March 3, 2023

To add a use case: We do sometimes use Primary Contact to indicate who the request is ultimately for. It's not unusual for a user to submit requests on someone else's behalf, then the work proceeds with the Primary Contact as a subject-matter expert or decision-maker for the deliverable. At the project level, that Primary Contact can be entered as the Sponsor.

Madalyn_Destafney
Madalyn_DestafneyAccepted solution
New Participant
March 2, 2023

WF's definition of Converted Issue Originator: A field in a project or task report that displays information about the user who is the Primary Contact of an issue when the issue is converted into a project or task. The field also displays in the Project Details section where it displays the name of the Primary Contact of the converted issue. 


And then related to above, Primary Contact:

The Primary Contact is the creator of an issue and it is automatically designated by Workfront when the someone creates the issue. You can manually update this field if you have Manage permissions to the issue. An issue can have only one Primary Contact. If you change the Primary Contact, the user originally designated as the primary contact still has Manage access to the issue. When converting an issue to a task or a project, the user designated as the Primary Contact of the becomes the Converted Issue Originator of the project or task. If the Primary Contact of the issue is updated after the issue was converted, the Converted Issue Originator will be preserved as the Primary Contact of the issue at the moment when the conversion happened.


Bookmark this useful WF terminology glossary! https://experienceleague.adobe.com/docs/workfront/using/basics/workfront-terminology-glossary.html?lang=en

If you found this useful, please mark correct to help others : )

 

If this helped you, please mark correct to help others : )
    S
    Sujatha_TS
    New Participant
    January 16, 2024

    Hi there, I was trying a task report where I need a column to see who the original requestor is (who raised the issue). 

     

    displayname=Requestor
    linkedname=convertedOpIssueOriginatorname
    namekey=view.relatedcolumn
    namekeyargkey.0=convertedOpIssueOriginatorname
    namekeyargkey.1=enteredBy:name
    querysort=convertedOpIssueOriginator:enteredBy:name
    textmode=true
    valuefield=convertedOpIssueOriginator:enteredBy:name
    valueformat=HTML

     

    is not helping. is there anything I am missing here ?

     

    Madalyn_Destafney
    Madalyn_Destafney
    New Participant
    January 16, 2024

    Hi there, you do not need text mode at all for that. 

    In your task report column, in standard mode, add this field:

     

    If this helped you, please mark correct to help others : )
    skyehansen
    skyehansen
    New Participant
    March 1, 2023

    hi there, "entered by" is the person who created the issue. "Submitted by" has more to do with approvals, so if you have an issue that is "New - Pending Approval" you will probably see that this was "submitted by". But largely this field (submitted by) is blank for our instance.

     

    I (and probably a lot of other more seasoned admins) usually advise that users key off the primary contact name, which also equates to the issue's "owner's" name. The owner CAN be the person who created the issue, and defaults to this when the issue is created. However, the primary contact name field CAN be changed if the issue ever changes ownership, as opposed to the entered by field, which usually cannot be changed.

     

    If you end up going back to a project report, you may find you have to build it from another name field, but the end result should look something like "convertedOpTask:owner:name"

     

      R
      R_KephartAuthor
      New Participant
      March 29, 2023

      If I wanted to key off the person who entered the issue what would that look like? Would it be convertedOpTask:enteredBy:name work? 

      Terms & ConditionsAccessibility statement

      Loading footer...