Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Setting start and end dates on JIRA calendar

New to the community. I've setup a JIRA calendar in Team Calendar, and want to set a start and end date to show the duration of a scheduled task. When I go to each task from Team Calendar, the "to" date in the "When" field is disabled. I would assume this would default to "due date" set in JIRA, but it is simply the "created date" (meaning both dates are the same). Is there a way to set a start and end date from a JIRA project?

I've seen mention of a ghant chart plugin, which seems helpful, but would like to try using the defaults first if they can achieve our desired effect.

3 answers

1 accepted

1 vote
Answer accepted

Hi Kiven,

Good question. Just to clarify a few things. At the moment:

* Team Calendars lets you visualise the start date of any issue date.

Out of the box in JIRA, you have "Created date" and "Due date". If you want, a lot of customers add custom fields in JIRA (e.g. Start Date, End Date, Deployment Date etc...) and you map them in Team Calendars

* Team Calendars lets you visualise the start and end date of any GreenHopper sprint

You just need to set the Sprint start and end date (which you do) when creating a GreenHopper sprint

* Team calendars lets you visualise the _due date_ for a JIRA version

Note: This is ONLY the due date at the moment. So it doesn't give you the duration. This is because JIRA did not have a concept of a "version start date" for a project. Only recently, JIRA now has a concept of a Version start date. So now we have the possiblity for team calendars to visualise the start and due date for a particular version for a project. You may want to watch /vote/comment on this ticket to stay updated:

Hope that explans the many different things you can visualise! It can seem like a lot, but it's quite powerful. Do any of those meet your needs or explain it a bit better?

Tsol Rising Star Oct 15, 2013

Hey Sherif,

i'm evaluating team calendars and i was trying to visualize the duration of a JIRA issue according to Planned Start and Planned End fields from JIRA Agile. From what i have seen only the start and end date are marked and not the duration.

Do i miss something?

Thanx in advance,


@kostas you need to select "add start and end date" for a date range:

then you pick the planned start and planned end dates from the JIRA issue.


I'm dealing with a similar situation: I would like to use 'Team Calendars' to plan the sprints.

Therefore, I understand that I need a custom field to add the start date.

For the end date though, I wouldn't hardcode it. I think it would be more useful for the team to use the estimation given for the issue. Is there a way to dinamically see this as end date in 'Team Calendars'?



0 votes

I have the same issue as you; I also tried Gantt Charts, they were rather an overkill for the intended purpose. Plus the performance was an issue. I'll post here if I find something useful!

0 votes
Gary Atlassian Team May 06, 2013

Hi Kevin,

First, welcome to the community - glad to have a fresh face!

Since Projects are meant to be static, there is not a way to set start or end date for a project. We would reccomend using versions in JIRA:

Sprints with Greenhopper:

or Epics with Greenhopper:



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events