I have created 3 new sprints and Future dated them. I working on creating dashboards for each of the sprints. When I add a Burndown chart I can only select current or pass Iterations but not any futures sprints . why ? is there a setting to fix this
Based on my test, I can reproduce the same situation when using Sprint BurnDown Chart.
The sprint burndown widget will display the current iteration (date) and the previous iteration. Future iterations will not appear in the widget until the start date is reached.
This is expected behavior and I am afraid that there is no method to avoid it.
For a workaround, you can change to use another chart: Burndown chart.
It supports custom time interval.
For example:
Related
could please someone enlighten me?
I have a data set and I need this data set to be refreshed on the 5th and 15th of the month.
But there can only be one schedule per Cognos object, right?
Is this the optimal solution?
I setup a schedule on the data set itself for the 5th of Month.
Then I create a job and add that data set as a job step.
I schedule the job containing that data set (which includes its own schedule) for the 15th.
What happens on the 15th and how these two schedules work with each other?
(This could also apply to reports etc).
Many thanks
I went through the documentation and some online articles, but there is no definitive answer if a data set (or a report..) can have multiple schedules set.
Lots here about reports and report views explaining how I handle schedules. Substitute "dataset" and "job" and I think you'll get what you want.
One schedule per object leads to limitations. I have found for reports that it is better to create a report view to handle the schedule. I very rarely schedule a report anymore because I often end up needing more than one schedule or set of parameters.
Using a report view provides a means to not only create multiple schedules per report, by creating multiple report views, but also have those schedules send the reports based on independent sets of parameters. For example, the regional VPs want reports showing their sales revenue for the month, but only for their regions. I would create one report, then create a report view for the U.S. and a report view for Europe. Both get sent on the 5th of the month.
Likewise, I could set up 2 report views to work around the scheduling limitations. Say I want to send the same report on the 5th and the 15th. I would create the report, then create 2 report views to handle the schedules.
So, to translate this to your need...
To refresh the same dataset on the 5th and the 15th, create 2 jobs that have the dataset as a step -- one job for each schedule.
Using jobs looks like the right thing to do for your use case. I don't see another scheduling option for datasets.
I am attempting to do historical analysis of call stats, the obstacle I am facing is that my agent's have the option of changing positions. For example Front/Back office, I would like to be able to differentiate their stats by role per year. If a front office agent is in front office from January to march, but then gets promoted to back office in April; I would like to time stamp their stats or perhaps create a table that references their time in that role to make sure the stats I am looking at are historically accurate. Currently I am using stats on a excel workbook and using power bi to visualize the stats year to date, and month over month. Right now I am encountering the fact when an agent's role changes their historical stats gets moved to their new position. I'm open to any suggestions or logic.
Currently trying to surface key information around the projects in our organisation. I want to show a breakdown of work items assigned, estimated time, and completed time per individual. I thought I could do this with the chart widget, and I can if I have 3 different pivots, but it seems very limited. I don't seem to be able to adjust the order of the column series (status) to what I want. I can adjust based on the values - e.g. estimates but then the next chart has that status in a completely different order because it's sorting on something different.
Is there another widget I should use, or is Azure DevOps not capable of handling this? Do I have to use Excel or PowerBI instead??
You can use “chart for work items” widget. Please select chart type as Pivot table. For example, here is my configuration of the "Chart for work items" widget:
You can see the Original Estimate assigned to each user in this widget:
I am trying to calculate the last working day for a process. Typically, this will be yesterday. However, if the process runs on a Monday it should bring back the date of Friday.
My calculation is:
Today()-MakeTimeSpan(1, 0, 0, 0)
Current code stage
The Best Practice in this area is to use VBO called "Calendars", that is a Internal one, built in the BluePrism.
Object: Calendar
Action: Add working days
Calendar Name: "Working Week / No Holidays"
Date: Today()
Days -1
An advantage of that solution is that you can customize the calendar to add all Holidays that are Bank Holidays for your company.
In the past, I've been able to accomplish this by using a dedicated Utilities object with an action that's just a single code stage. The action has a single Output connected to a single output of the Code stage.
out = DateTime.Now.AddDays(-1)
While out.DayOfWeek = DayOfWeek.Saturday Or out.DayOfWeek = DayOfWeek.Sunday
out = out.AddDays(-1)
End While
This also opens the ability for you to add complex logic to account for holidays in your locale(s) without cluttering up your action page.
Is it possible to start a workflow automatically the first day of every month?
Edit:
In principle I think this has to be programmatically although if it can be achieved using an out of the box features it'd be easier.
Yes, you can start workflow using 2 diffrent approch as below.
Create one timer job which will run on every first of the month & kickoff the workflow programatically.
Create custom workflow which will run when item added but wait until 1st date of the month.
You can try creating a workflow for the list you are monitoring and set the action to wait until the 1st day of the month before doing the rest of the actions.