Project Status not showing in preferences | Community
Skip to main content
J
JAMIEDE
Level 2
May 15, 2024
Solved

Project Status not showing in preferences

  • May 15, 2024
  • 3 replies
  • 1763 views

I am currently working through our oversized catalogue of statuses and I can't figure something out for the life of me. It's probably super obvious and I'm just missing it.

We have a number of Projects with the Status: Active. 

When I go into Project Preferences - Statuses - Project = there is no status that exists called Active.

We convert our projects from Issues, so I checked Issues. There IS an Active, but it's not the same colour as the one that shows for Project Status.... 

Can anyone help?? 

 

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 lgaertner

Hmmm. So the Issue ALWAYS go back to New once it's converted to a Project? So you would need to go into the details and see if it was linked to a resolving project every time? 


Hi,

 

in general my suggested route would also be Fusion.

 

But you need to be careful:

As soon as you convert an issue to a task or project and you chose the option to keep the original issue (preserveIssue), the status of the issue is not editable any more, as it is depending on to the resolving object status. 

 

This dependency is only decoupled when the resolving object is completed.

What we have done (also using Fusion):
After the conversion the resolving task is set to the status completed for a moment and set back to new shortly after that to keep the original issue on completed while keeping the connection between issue and task.

 

If you have a look into the API Explorer, you will see, that there is a boolean field for issues (OPTASK), called isComplete, which is changed from false to true, if the resolving object is completed.

 

Regards

Lars

3 replies

J_Mas
J_Mas
Level 5
May 15, 2024

Is the Status applied at the Group level? In the upper-right corner where it says "System Status" try entering the name of a Group that you know has access to that Status. Different Groups can have different Statuses.

lgaertner
lgaertner
Level 9
May 15, 2024

Oh, sorry, 

I did not see, that you already answered J_Mas.

    lgaertner
    lgaertner
    Level 9
    May 15, 2024

    Hi,

     

    I would suggest checking, which group those projects are associated to under Overview -> Project association.

    If you open that group under Setup -> Groups, have a look under the Status tab there.

    You can also jump to that group using the input field on the top right of your first screenshot.

     

     

    Regards

    Lars

    J
    JAMIEDEAuthor
    Level 2
    May 16, 2024

    OK, so I now see the Group level - however I feel this has made it even more confusing! lol.

    Essentially, I want to make it so when I convert an Issue to a Project, the status of the Issue is no longer new, so people know it's being worked on. For example, it would be good if once converted to a project, the original issue status changed to Prioritized. 

    Any insight on how I can do this? 

    J_Mas
    J_Mas
    Level 5
    May 16, 2024

    I think the only way that this can be done is with Fusion (although @lgaertner might know something I don't).

    skyehansen
    Community Advisor
    skyehansenCommunity Advisor
    May 19, 2024

    I'm going to leave the fact that you have problematic statuses alone -- this is a governance issue on your part. I suggest for your other question (how to make it so that the issue status reflects what the converted project is doing) you read the following article:

     

    https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/issues/convert-issues/resolving-and-resolvable-objects

     

    Especially this section:

     

    https://experienceleague.adobe.com/en/docs/workfront/using/manage-work/issues/convert-issues/resolving-and-resolvable-objects#synchronize-the-custom-status-of-the-resolving-object-with-the-custom-status-of-the-resolvable-object

     

    On our side, we created (and hid) a number of issue statuses at the system level, that directly correspond with project statuses at the system level via 3 letter code. Say if we have a project status BlahBlah with three letter code BLA, then we make an issue status called Project:BlahBlah with three letter code BLA. Now, when we convert the issue to the project and we change the project status to BlahBlah, the issue status will change to Project:BlahBlah. Which is what I believe you to be asking about.

     

    (We hid these issue statuses because we don't want users to use them manually. They are only used when the system links two objects.)

      J_Mas
      J_Mas
      Level 5
      May 20, 2024

      This makes me want to create a project status of "Problematic". I think I'd have a few good use cases for it. 

      🙂

      skyehansen
      Community Advisor
      skyehansenCommunity Advisor
      May 20, 2024

      I mean, as long as the status is hidden, is it really Problematic?

        Terms & ConditionsAccessibility statement

        Loading footer...