While implementing HC gantt chart with tree grid and sub tasks I noticed that in the samples collapsing an item with children would show the details of the children, but not always.
Looking at standard project management example (jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/gantt/demo/project-management) if we collapse the "New Offices" node, it will show a summary of the children underneath, but if we collapse the "New Product launch" node, then it doesn't show any details. Why are those 2 nodes performing differently? In my case I'm never seeing details but this might help find the required conditions.
It is a bug, which has been already reported and fixed. Should be fine in the next release.
See: https://github.com/highcharts/highcharts/issues/12617
Related
I would like to be able to highlight a row on a backlog in much the same way as you can with styling rules on a board view of the backlog. I want to be able to add a tag called "QA Ready" and then any row that matches the criteria to be highlighted.
There is no styles for backlogs. You may post your idea to Developer Community or use excel integration with built-in styles for cells. Or create a custom report.
We have created couple of jobs under different different project acronym, which is visible in All the tabs on jenkisn dashboard. But it is not coming for the corresponding views.
e.g.
aat-CWM-fe-APP_MAIN_MAVEN-snapshot should come under aat
kps-MVW-be-kps-online-snapshot should come under kps
I tried to search in SO, but did not get any much help. Please consider this as my scrolling time and provide the solution.
Some of the question , I have gone through for help:
Jenkins restrict view of jobs per user
How to tell if UIViewController's view is visible
How to add a new job to a view in jenkins via python-jenkins?
As far as I know, Jobs will not be visible in newly created Jenkins tab/view because of these two reasons:
You might have created other than List View like Dashboard view or Nested View.
You might not have selected the checkbox "Show standard Jenkins
list at the top of the page " under Dashboard Portlets
So, the resolution will be :
Create a list view, as dashboard view is more of a consolidated view to any job.
Select the checkbox "Show standard Jenkins list at the top of the page " under Dashboard Portlets.
If any other reasons are there, someone please update.
I have created multiple area paths for each module in our system.
When working in the Backlog I'd like to filter backlog items for one of the modules (Area Path). I could not figure out how to do that, so I simply added the Are Path field to the Backlog view and used the Filter for filtering on the requested module.
This worked, but when there are Tasks associated to the backlog item, they also show up in the Backlog, which quickly pollutes the view. Is there another way to either enable filtering on Area path or hiding Tasks from the backlog view?
The filter box in the (Product) Backlog view only works on keywords, unfortunately, and you can't exclude items. There is also a Tags filter. If you click the filter button, you can click the tags you want to include. This would require you to add a "backlog" tag to all the items you want to show (excluding tasks, of course) but, even though it works, it's not a great solution, because you have to manually add the tag to the work items you want to display.
If you're not tied to the Backlog view, you could switch over to the (Kanban) Board view. There is a more advanced filter there. Click "Board" at the top, then the filter button in the upper right, and then you can filter according to work item type and other values. This is probably what I would do.
The third option is to convert your view into a query by clicking Create Query at the top of the backlog (or just manually writing a new query). You can then edit the query to exclude Tasks. The advantage is that it's a lot easier to control what work items you see (or don't see), and how you see them. The disadvantage is that you lose the ability to drag-drop for stack ranking, and other backlog features.
I have a report created with Digital Metaphors ReportBuilder (VCL edition, in Delphi XE3).
It's an invoice, with header, detail and footer bands.
When the data fits in one page, all is well.
If I have more data, that fills, lets say for the sake of argument, 2 pages, I would requires:
Footer band only in the last page
On all other pages, the footer band should be replaced with only the running amount from the detail band, up until that page (from the first one).
On all but the first, the header should include the running totals of all previous pages.
Something like:
Page 1:
- (Header)
- Detail
- "Value until now: (Sum of one the the fields present in the detail band)"
Page 2:
- (Header)
- "Value until now: (Sum of one the the fields present in the detail band) of previous pages"
- Detail
- Footer
I've tried to investigate group totals, using a DBCalc component, but those aren't aware of the page. It only shows the total in the end, and not at the end of the page.
Any pointers of how I could do this?
Thank you
You will need to make some use of the Calc tab, in order to decide when you want certain bands to be shown or hidden. The Report has a PageNo property which you can use to decide when to show a header or a footer, in the header or footer's BeforePrint event.
As for showing a running total at the bottom of each page, you could use a ppRegion component (which is the ReportBuilder equivalent of a Panel). Again, you can use the BeforePrint event to decide when this shows.
The running totals themselves should be done using ppVariables. As you traverse through the data, add values into each variable that you need. Put these variables in the Region mentioned above, and they will display the value as it is at the end of each page. Timing can play a part here, so you may need to adjust the Variable's CalcType, ResetType, CalcComponent and ResetComponent properties to fit your needs.
I have been using ReportBuilder for almost 10 years and believe me, everything can be done, but some operations may just take time to perfect. We now use it exclusively in our software, both for the standard reports that we issue with our product (over 300) and for users to create their own reports.
I am trying to display items retrieved from an XML DB using xforms:select1 control using appearance=xxforms:tree. The items appear collapsed or expanded automatically and the behaviour is not the same for all the items retrieved. I have the following questions regarding xxforms:tree view:
how to make sure this view shows sub-nodes (those expandable/collapsable using +/- icon) as collapsed or expanded always, irrespective of, for example, the no. of nodes covered by the + icon?
how to render select1 with tree appearance without making any of the items hyperlinks?
how to make sure no item is highlighted/selected by default?
...and although the docs say xxforms:menu is also a possible appearance (URL http://www.orbeon.com/orbeon/doc/reference-xforms-extensions#tree), the details are not available...
About which branches of the tree should be open — By default all the nodes leading to selected nodes are open, this so the selected values are all visible. But you can change this default behavior and specify which nodes should be open using the xxforms:open attribute. For more on this, see the section "Controlling which tree nodes are initially open" on Selection Controls. Note that this feature was added in October 2010, so it is not included in Orbeon Forms 3.8, and until Orbeon Forms 3.9 is released, you'll need to get a nightly build for this.
About using links in the tree — At this point, the nodes you can click on in the select1 appearance="xxforms:tree control are rendered as links, so users know that this is something they can click on to make a selection. I assume that you don't want them to show as links because the tree might be "read-only" in your case (for information only, not to make a selection). This isn' supported at this point. As a workaround, you could use CSS to change the pointer and appearance of links in the tree so to users they don't even notice that this those are links.
About the menu appearance — It works very much like the tree appearance. See for instance this example using the menu.