Using latest fullcalendar.io, the number of weeks that are displayed in month view is appropriate for the first month that renders. When using the prev/next buttons, if the next/prev month has less weeks than the current month, it still renders the current month's number of weeks.
Right now it's May 2015. The demo on the site is here: http://fullcalendar.io/js/fullcalendar-2.3.1/demos/gcal.html
May 2015 renders with 6 weeks, because that's how many are needed. When I click next to go to June 2015, 6 weeks are still rendered in month view, even though only 5 weeks are needed.
Question: how can the number of weeks that gets rendered adjust to the actual number of weeks that a given month has? This means that May 2015 would have 6 weeks, but the table would reduce to 5 weeks for June 2015.
This is important when trying to print a monthly calendar. It's May right now, but someone might want to click next and print June, which is coming up. The June calendar should only have 5 weeks, but I can only make it display with 6, since I entered June from May.
Thanks for only tips on this.
ryan
Your looking for the fixedWeekCount option. From the documentation, you can see that:
If true, the calendar will always be 6 weeks tall. If false, the calendar will have either 4, 5, or 6 weeks, depending on the month.
So, if you want to display the correct number of weeks per selected month, you should set that option to false when fullCalendar is initialized:
$('#calendar').fullCalendar({
fixedWeekCount: false
});
Take a look at this jsfiddle for a working demo.
For those poor souls who are still stuck with older version of fullcalendar (v1.6.4) use:
weekMode: "variable"
Related
I wanna display the time spent per issue in a specific timeframe. Creating a rich filter that shows time spent is very straight forward, however, selecting the right timeframe is tricky.
Possibility #1:
resolved > -12w
That selects issues resolved within the last quarter, but then all time is displayed, even when the issue is is much older and a lot of time has been booked more than 12 weeks ago.
Possibility #2:
created > -12w
That selects issues created within the last quarter, and automatically excludes issues that are still being worked on but are older
Possibility #3
created > -12w and resolved < -4w
That selects issues created and resolved and disregards issues going between timeframe boundaries.
Possibility #4
worklogdate > -12w and worklogdate < -4w
That would select only issues with correct worklog dates, i.e., issues that REALLY have been worked on in that timeframe, but when I then analyze worklogtime or time spent, that is still all the time worked on the issue, not just the time within the specified timeframe.
Any idea how I could achieve showing the time spent per issue of a very specific timeframe?
JIRA's time spent calculation seems to be adding quite a few hours to actual time spent.
If I add up the columns I get a much different result than when JIRA adds up the columns.
My question: How does JIRA arrive at this amount of time tpent in the default time tracking report?
Edit: Maybe a JIRA "day" is 8 hours? That seems silly to me...
It turns out that by default 1d is not a real day, but it's a Jira day, which is 8 hours apparently.
1 day is one working day, of course. This is an issue tracking and project planning system what else could "a day"?
Also this is configurable in JIRA...
Does anyone know how to filter issues in a given project to show only issues that were created between 5pm and midnight for an entire month?
I am able to constrain between 5pm and midnight on a single day as below but am unsure how to make it do the whole month:
project = CI AND issuetype = "Activity" AND (created >= endOfDay('-1860m') AND created <= endOfDay(-1440m))
Had to write a JQL function using the GroovyRunner plugin in JIRA.
Am having some performance issues which I will put in another StackOverflow question
EDIT:
Performance issue post available here: https://stackoverflow.com/questions/18606967/jira-jql-performance-issue-with-custom-function-in-groovyrunner
I want to specify the team capacity per user and per activity on TFS'12 Scrum Template 2.0, which may differ on every day on the sprint.
As described in http://msdn.microsoft.com/en-us/library/ee191595.aspx I can set capacity per day of a person, like 7 hours for a sprint of 5 days.
How can I specify a capacity like the one below?
Day 1 : 7 hours
Day 2 : 5 hours
Day 3 : 9 hours
Day 4 : 3 hours
Day 5 : 6 hours
Thanks.
As others have mentioned, the TFS capacity planning doesn't support this. You can use the "Days off" to block off entire days, but not parts of a day.
That being said, the capacity planning is used to try to know how much work is assigned to an individual or team and whether you have enough capacity left to address the work remaining. For the majority of your sprint, an average will work. For risk-averse managers, you may want to put in the minimum amount and just use the additional hours as bonus that is not part of the capacity.
In your specific example, however, if your individual is averaged to 6 hours a day, you'll get a capacity that starts hurting you at the end of your iteration. It will look like you have 12 hours left for Day 4 and 5, but really you only have 9 hours.
If you use the minimum approach, you'll average at 3 hours a days and look like the capacity is full part way through Day 3 if you assign tasks that fill up their actual hours.
This is one of the reasons that you should be trying to get a consistent availability from your team, and not just having an hour here or there being added to the sprint. 100% allocation, ideally, as you'll read about on most anything written on scrum/agile teams.
In the end, also, you need to ask yourself what you are going to use the capacity numbers for. That will dictate whether this is the right tool for what you need to accomplish, and also what approach you can take.
It is not possible to set the capacity on a daily basis (unless of course, you have a 1 day sprint). The easiest solution would be to find the average availability and put that in for the individual's capacity.
Generally speaking however, individual capacity isn't what is important in Scrum, the Team's capacity & velocity are.
If you want to have this level of detail in your planning, I'd suggest to setup Project Server Integration
PLEASE SEE THE EDIT BELOW, THE REPORT SEEMS TO USE CACHED DATA?
I cant figure out why there are 89 hours of work remaining, when I have 3 Active Work Items totaling 44 hours:
My Burndown Chart:
Remaining hours on 3 blocked tasks equals 44 hours:
I do set the completed hours when I close my tasks:
What am I doing wrong with the remaining vs completed hours? is this a bug in TFS?
This seems to be different to previous experiences, I've just started a new job.
EDIT:
Today the report is correct, how do I stop the caching happening?
This burndown report reads from the cube and not from the operational datastore. The cube is processed every 2 hours.