In my JIRA structure with the Gantt plugin, I would like to have the Start and End Dates for Features in my Gantt view be specified by its children's MIN "Target Start" / MAX "Target End" Dates (children like Epics).
eg: Here are the formulas I would normally use in Structure column >>
Hello @Joel Sanders
The formula you're using is correct - it should return min or max date taken from sub-issues of each Feature. Please keep in mind:
- to apply the formula, the 'Treat parent issues as groups' option in the chart's settings (the Scheduling tab) should be disabled. Otherwise, the formula won't work for parent Features at all, and each Feature's Start & Finish date will be calculated automatically.
- if you schedule sub-issues of features by Target Start/End dates, then you might not even need to use the formula at all, and you need to have the 'Treat parent issues as groups' option enabled. In this case, Features' start will be calculated as the earliest Target start of sub-issues and finish will be equal to the latest Target end. It's the default logic of how groups are being scheduled.
I hope this helps. If you need further assistance or have other questions about Structure, please reach out to us directly at our support portal.
Best regards,
Stepan
Tempo (the Structure app vendor)
Thanks @Stepan Kholodov _Tempo_ - I've tried the following based on your feeback (for image captures below >> at left is the settings, at right is the gantt view) \/\/\/
- My current view >> Manual Scheduling leveraging Target start/end w/ "Treat parent issues as groups" DISABLED --> I see both Feature & child Epics display correct Target Start/End
- Attempt to use Manual Scheduling leveraging target start/end w/ "Treat parent issues as groups" ENABLED --> I get a weird shift where both Features & child Epics are no longer accurate in relation to their Target Start/End
- Attempt to use Manual Scheduling set to leverage Formulas w/ “Treat parent issues as groups” NOT selected --> I get a weird shift where the Feature & child Epics are no longer accurate in relation to their Target Start/End
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Joel Sanders
It's not very clear to me what you're tryiong to achieve here exactly. On the last screenshot - the 'Treat parent issues as groups' option is disabled and the formula is used as the Start Date in the configuration of the chart - it looks like the Feature at the top is getting the expected dates. As for the issues underneath it - I assume these are not Features, and since the used formula only works with Features and no other issue types, these issues are scheduled on the chart automatically. If you want them to be scheduled by their Target start/Target end dates, you need to add another condition in your formula to ensure that it works with issues other than just Features:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Joel Sanders.
Because you are using Structure from Tempo, I moved your post here to App Central, which is the right place to post questions about Atlassian Marketplace products.
I also added a couple of additional tags to your post to help draw the right eyeballs to it.
The Structure support team is good about keeping an eye out for Structure things here, but the extra tags will help.
Best,
-dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.