Roadmap>Epic>Story // How to set the time frame?

[Domo]

Hi

after creating some issues and sprint, I'm now on the way to create a roadmap. (The sprints are only important for the preparation of my business.)

After creating some epics I've created also some stories. But as you can see below, I can't put the time of the first story according to the epic which it belongs to. That is not logical, is it? I mean, normaly the dates of all of the stories create/define the date of the epic. What do I wrong?

[Trudy Claspill]

Hello @Domo 

You need to change the configuration of your Timeline to schedule child issues based on dates rather than sprints.

[Domo]

Great. That is what I was looking for.

[Domo]

By the way,

do you know how I can define the dependenced betweet two stories, like in regular gantt charts? F. e. story 2 depends on story 1 in such a way that story 2 begins exactly seven days after story 1 (no matter how story 1 changes).

In most project-management tools the definition for story 2 would be e.g. as follows: '1AA+7 days'.

[Trudy Claspill]

You define the dependency by using the Link Issues function and using the "blocks/is blocked by" relationship.

The basic Timeline function does not include automatic scheduling between dependent issues. 

If you want a successor issue to change its start date automatically based on changes made to the dates of a predecessor, you would need to manage that with Automation Rules.

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

[Domo]

1) "You define the dependency by using the Link Issues function and using the "blocks/is blocked by" relationship."

Where can I find the 'link-issue function'? When I click on the link line there are just some details and the possibility to remove the link but nothing more:

[Domo]

2) "The basic Timeline function does not include automatic scheduling between dependent issues."

Actually, I don't need any automation. I just need to set the dependency individually. That means, not only what depends on what but also how it depends. Like in the avarage project management tools. 

[Trudy Claspill]

When viewing issue details you can use the Link Issue button to create a link between the issue you are viewing and another issue.

[Domo]

This is what I can see. 

But there is nothing like the standard project-plan-issue settings.

[Trudy Claspill]

Refer to the image below.

(1) is the same button I pointed to in my image, used to initiate the Link Issue function.

(2) is the area where you actually create the link. You select the link type on the left, and enter the other issue's key on the right.

If the task you are currently viewing is dependent on completion of another task, select "is blocked by"  as the link type.

If the task you are currently viewing is the predecessor to another task select "blocks"

[Domo]

Hmm, I think that's exactly how I understood it before.

I understand the terms too.

Let's assume the following case.
Issue 1 should be followed by issue 2, with a buffer of 2 days being built in.

Where can I enter the buffer? So e.g. E.g. something like 'blocked by ... and 2 day buffer'.

[Trudy Claspill]

There is no built in field to enter a buffer value. You would have to add a custom field for that.

And the, as I said in my second response, if you want to automate the setting or changing of dates on successor task you can do that with Automation Rules.

However you will face limitations with Automations. 

1. The rule to update successor tasks would be recursive. There is a limit of 10 recursive calls for Automation rules. If you had a chain of more than 10 dependent tasks the rule would not be able to update them all.

2. There are changes coming to how rule executions will be counted, and each plan has a limit on how many rule executions you are allowed. The limit on the Free plan is the lowest and may not be adequate for your needs.