CONFIRMED: New Project - I'm the creator & owner - Cannot add myself to project or create releases

[njacobs125]

Hello! I created a new Imhotep Project, I am the owner. I'm getting errors when trying to add release & project member.

[egyptguy]

Hi @njacobs125! Yes, a couple of customers have reported this in some other channels, I forgot to log this as a Github issue. This occurs occasionally when creating a brand new project. I'm working on a fix in the next release - for now, the easiest thing to do is delete the project and create a new one. It doesn't seem to happen back-to-back. Sorry for the trouble!

For reference, the issue appears to be caused by an order of execution issue in the flow - the initial backlog release and project member records aren't created because the project record isn't finished being created. It doesn't appear to happen often, but I'll post back when an updated package with the long-term fix is ready.

• Mitch

[njacobs125]

Thanks for the fast response, Mitch! I deleted the project and created a new one. Same experience. Is there any possible chance of getting on a quick call? I'm happy to try whatever. I've been at this for an hour :-/

[egyptguy]

@njacobs125 gotcha - well I suppose "occasionally" is no longer accurate, I'm sorry about that. A system administrator can still create a project member record manually - from App Launcher, go to the Project Members tab. Use the New button to create a project member (selecting your project and choosing Owner/Lead for the role). The sharing rules will be automatically applied.

If that doesn't work, I can jump on a quick call - shoot me an email for a Google Meet or you can send me one of your own [email protected]

[njacobs125]

Trying now... thank you!

…

On Fri, Oct 11, 2024 at 8:37 AM Mitch Lynch ***@***.***> wrote: @njacobs125 <https://github.com/njacobs125> gotcha - well I suppose "occasionally" is no longer accurate, I'm sorry about that. A system administrator can still create a project member record manually - from App Launcher, go to the Project Members tab. Use the New button to create a project member (selecting your project and choosing Owner/Lead for the role). The sharing rules will be automatically applied. If that doesn't work, I can jump on a quick call. — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL7EUMZUSXUMFICN65Y52TTZ27A7TAVCNFSM6AAAAABPYZFN2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBXGMZDMMBSGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *Nancy Jacobs *| Senior Delivery Manager & Sales Support Specialist Schedule a Call <https://calendar.app.google/rYqHNKbhwre8FJae6> Confidentiality Notice: The contents of this email and any attachments may contain confidential and/or proprietary information, and are intended only for the person/entity to whom it was originally addressed. Any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this email in error please notify the sender immediately by return e-mail and delete this message and any attachments from your system.

[njacobs125]

That worked! Thank you!!!! On Fri, Oct 11, 2024 at 8:37 AM Nancy Jacobs ***@***.***> wrote:

…

Trying now... thank you! On Fri, Oct 11, 2024 at 8:37 AM Mitch Lynch ***@***.***> wrote: > @njacobs125 <https://github.com/njacobs125> gotcha - well I suppose > "occasionally" is no longer accurate, I'm sorry about that. A system > administrator can still create a project member record manually - from App > Launcher, go to the Project Members tab. Use the New button to create a > project member (selecting your project and choosing Owner/Lead for the > role). The sharing rules will be automatically applied. > > If that doesn't work, I can jump on a quick call. > > — > Reply to this email directly, view it on GitHub > <#7 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BL7EUMZUSXUMFICN65Y52TTZ27A7TAVCNFSM6AAAAABPYZFN2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBXGMZDMMBSGU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- *Nancy Jacobs *| Senior Delivery Manager & Sales Support Specialist Schedule a Call <https://calendar.app.google/rYqHNKbhwre8FJae6> Confidentiality Notice: The contents of this email and any attachments may contain confidential and/or proprietary information, and are intended only for the person/entity to whom it was originally addressed. Any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this email in error please notify the sender immediately by return e-mail and delete this message and any attachments from your system.

-- *Nancy Jacobs *| Senior Delivery Manager & Sales Support Specialist Schedule a Call <https://calendar.app.google/rYqHNKbhwre8FJae6> Confidentiality Notice: The contents of this email and any attachments may contain confidential and/or proprietary information, and are intended only for the person/entity to whom it was originally addressed. Any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this email in error please notify the sender immediately by return e-mail and delete this message and any attachments from your system.

[egyptguy]

@njacobs125 whew! Sorry again! I'm trying to use as much configuration as possible in the app so that the flows can easily be rewired by a non-developer who wants to tailor them for their own processes... so I need to rework the New Project flow to make sure this doesn't occur and fight the desire to write any Apex :). Thanks for bearing with me - this issue came up well after beta testing, which makes me feel like something became much more performant in Flow in the Summer '24 release (which is a good problem to have, I suppose!).