Sometimes the created project is not visible to the user

[Manjusha M I]

When we create the project using forge API, it is been created successfully, but it is not visible in the UI or API.

when we try to create another project with the same name, it fails saying the project already exists 

#forge #jira_service _management 

[Joseph Chung Yin]

@Manjusha M I -

Welcome to the community.  You will need to look at the project that was created by your forge API via Project settings >> Customer permissions to determine what is the configuration it got set.  Another thing that you need to review is the project's permission scheme setup.

If you create a project via the JSM project UI, is the same issue happens where users cannot see the project?

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Manjusha M I]

Thanks for replying 

all the permission has already been given and it's not created using JSM it's created using forge API 

Here are some more details 

const body = {
    assigneeType: "UNASSIGNED",
    avatarId: 10200,
    description: "Jira Experience Builder Project",
    key: "JEB",
    leadAccountId: req?.installerAccountId
      ? req.installerAccountId
      : req?.upgraderAccountId,
    name: "Jira Experience Builder",
    projectTemplateKey:
      "com.pyxis.greenhopper.jira:gh-simplified-agility-kanban",
    projectTypeKey: "software",
    url: "https://community.atlassian.com/",
  };

const response = await api.asApp().requestJira(route`/rest/api/3/project`, {
method: "POST",
headers: {
Accept: "application/json",
"Content-Type": "application/json",
},
body: JSON.stringify(body),
});

[Joseph Chung Yin]

@Manjusha M I -

As I mentioned before if you create the project via the project UI (not using Forge APIs), did the created project behaviors the same way with the one that you created using your Forge APIs?

Please also provide screenshots of your Customer permissions configuration and project permission scheme for us to review.

Best, Joseph

[devpartisan]

@Manjusha M I

I've tried to reproduce the behavior you describe via a simple HTTP client. My request gives me a reference to the project right away:

{
"self": "https://devpartisan.atlassian.net/rest/api/3/project/10787",
"id": 10787,
"key": "JEB"
}

Furthermore, I see projects in my "View all projects" UI nearly immediately. So the problem doesn't seem to be widely observable. Before we try to troubleshoot further here, I would ask for a "change of venue".

First, you posted into the user community, not the developer community. While many users are excellent developers and well-versed in the Jira REST APIs, I think your line of questioning would be better suited to the focus of our developer community.

Furthermore, you have posted this question in the Jira Service Management category, but your problem is with the Jira platform APIs. In fact, the kind of project you are creating is actually a Jira Software project. Either way, not JSM. Please use categories and tags appropriate to get the right domain experts engaged.

Finally, I agree with @Joseph Chung Yin's implication that this isn't normal behavior of Jira but is probably isolated to your instance. Joseph was following the most likely case, where admin-level configuration (in the form of permissions) could be "hiding" a project from both UI & API. However, there are other possibilities that might be unique to your app and/or instance. Because of the unique nature, I recommend asking developer support and reporting as if you have a bug.