Anyone edit the project go lives widget?

jonathan_luste · ‎12-05-2016

So I was adding widgets to a dashboard, and saw the Project management type, and there was a Go Lives thing to add. I love it, but it shows too much and I want it to be filtered. But I cannot find where it lives / is editable or clonable.

What I found is this:

Briefly mentioned on the docs site : CIO Dashboard

UI page is called projectGoLives.

UI page script contains "iframe src="/$project_go_lives.do""

And that's all I can find. No where do I see source data controls or filters.

Anyone have a clue?

jonathan_luste · ‎01-11-2017

Not by default it isn't. That's true. However we were able to do it, and I want to share that.

The project go lives as I see it is a UI page that runs .js. The location of the js is here: /scripts/project_go_live_widget/get_project_go_live.js. (Note, there is also a css that is needed, but we didn't mess with this, located here: styles/project_go_live/project_go_live.css)

Now, us mortals cannot edit this, but we can see it, and copy it.

What we did was to copy it, and create a new UI page "tps_go_lives_code" and insert the js copy into the client script section. (we did make one change to line 44 (inner html) to make the projects URLs that open in a new window).

As far as the data filter, that's driven by a timeline (for roadmap). So we made one and edited the lanes and panels to be what we wanted.

To be able to render the widget AND have the widget render the data, we needed to have two UI pages, one for the code, and one for the widget.

so, tps_go_lives, which basically calls the tps_go_lives_code in a frame

View solution in original post

Matt Hernandez · ‎04-10-2019

This same thing happened at our place today. An admin/report developer put that widget on a dashboard, but the query wasn't quite what we wanted so I set out looking for the source.

Turns out the query is defined in the settings: configure: Panel condition area on the CIO Roadmap page. Whatever query criteria you have left in there is what the widget uses.

We noticed the widget showing different results for two different viewers of the dashboard, since we each had separate queries defined in our Roadmap configurations. Since the goal for our dashboard was a specific query of projects, and since maintenance of that would be completely not intuitive to us, we elected to NOT use that widget on our dashboard.