Jump to content

Recommended Posts

Posted

Hi

In a project template, I added a stakeholder and gave them the role of the PM. I hoped this would assign them as the PM when the Project was created via the integration call from Service Manager using the Project Template. However, it didn't and I was still the PM because I created the project. 

Is that by design or is that something that could be looked into? 

Thanks

Posted

@Darren Rose the iBridge nodes have been updated to give you the chance to specify a project manager on project creation. You can do this by selecting a co worker from the drop down or by injecting the project manager as a variable.

When a project is created, if a project manager has been provided, the system will use them as the project manager and will ignore the application setting that sets the project creator as the project manager. 

If no project manager has been provided on project creation, the system will check the app setting and if it is enabled, it will set the project creator as the project manager.

 

This will all be available as part of the next project manager update.

 

Alex

Posted

@Darren Rose a new update is available in the app store which fixes this issue. Interestingly though, this error would only have been possible if the new task failed to create in the first place. There may be another issue with the task you are attempting to create.

 

Alex

  • Like 1
Posted

Thank you @alextumber that seems to now be working ok, but I am unable to set a project Manager via a variable though. The field always remains blank... 

I have tried using the inject and overwrite options

 

image.png.36f823288966a609ec67d4a194f6649d.png

  • 1 month later...
Posted

@Darren Rose The next update to the Hornbill Admin Tool will make it possible to insert variables into an iBridge node param that contains a search box. We expect this update to happen sometime over the next couple of days.

image.png

 

image.png

Alex 

Posted

This is great. 

We have run into a small practical issue with the latest update, whereby we cannot change the owner of a task, but only the assignee. Due to the issue we had with the ibridge, we had to hardcode a PM into ibridge, and change it after the project was raised. Since the updated version was released, we cannot change the owner of the tasks so they're now all owned by the default PM... does that make sense? 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...