Curt Holley Community Champion

Regarding your automation, i think the simplest solution would be to create a manual trigger version of it that you evoke from the epic and it creates the story and associated tasks. This could be as well as the one that works in native Jira. Then instead of creating the story in AR, open the Epic (from AR), run the manual…

Hi @Darrel Jackson I believe it happens due to not being able to create a story in AR with the Epic link populated as part of the (virtual/staging) creation. See my below experiment. I created a story via AR, immediately associated with an Epic and then gave it a start date. When you review the changes, it shows created +…

Following on from @Dave LIAO banger, this is one of my fav remixes for the year. Guaranteed to rock the office party: INXS NEED YOU TONIGHT PIERRE M 2021 NEED A BOOGIE REMIX - YouTube

Correct @Sam Harding working now I've made it {{customfield_10298.fullDate}} Thanks for that. This is a great enhancement of the Look-up issues action.

Glad you sorted it.

Hi @Daniel Borisov Welcome to the community. This should be able to be done. It would be good if you could show us what issue sources your plan is using and what you are seeing. I take it you are using boards that filter on all issues (be it stories, Bugs or Sub-tasks) per team member??? If so, then these should ALL be…

You could do it via the Context of the custom fields, but you will run into the same (Admin overhead) there, if you have to move out of Global project setting and having to select each project you want it viewed on. Personally, I don't know if there is a way to do this via Scriptrunner cloud (sounds like not). Perhaps ask…

So I should be able to get custom date fields, is that right? @sam As I'm experimenting with such a field, but nothing is coming through. Using: {{issue.customfield_10298.fullDate}} FYI, doesn't seem to matter which date format I try

Welcome @Michelle Price post a recent decent photo you have taken. #just for fun 😊

In that case I have to wonder if it would make may sense to change tack and make children of the Initiative?? If these Epics are so crucial to this initiative that you want to derive its Story point total, then surely they should be hierarchically linked (using the Parent link field). This would be playing to Jira's…

Very true....there is nothing like "Being there".

Much as I would love the opportunity to actually meet other community leaders and go to Team 22 (or the like), for me, being in New Zealand means this was always going to be a hard/expensive/time consuming effort. As even if held in Australia, as then many of the northern hemisphere folk, wouldn't be there,…

Are you talking about "parent link" (I.E. the epics that are children of the initiative) or just standard JIRA "linked issues"? As, using the "Parent link" field with an Advanced Roadmap plan and Story points "rolled-up" feature enabled means you can get the affect of "summing", without the need to automate at all. See…

By using different screen schemes for the different projects. Check this out. Specify field behavior | Atlassian Support

You could do this with Automation for Jira. Of course you would need to ensure you have the relevant fields in the Epics, or can map to existing fields in your epics.

And you @Dhanyasri If you could Accept the answer these will help others with the same or similar questions find and confirm the answer. cheers Curt

So you are using the plug-in on a server/DC instance of Jira I take it? Regardless, I doubt that Program would be an option for the advanced roadmaps plans on confluence macro. As it is for sharing a view of a plan, not a whole program of work.

HI @Dhanyasri Welcome to the community! What is your definition of "Program" in this instance? Do you mean, can Advanced roadmaps be a confluence App instead of a Jira App? If so, the answer would be no, as it is part of Jira Premium (on Cloud) and a Jira plug-in (Portfolio for Jira) for DC/Server.

I agree with @Mykenna Cepek and @Bill Sheboy and think you are going to struggle to take full advantage of the tool if you don't go beyond "general" rules. Hard to know how to advise further without more detail on the purpose of the rule. I'm supporting 1400 users, hundreds of projects and teams. Use many global and multi…

Exactly @Mykenna Cepek 

Question: Are you using the Advanced Roadmaps (AR) based Team field (from the Shared teams section of Plans) or just a custom field of your own making? As the AR Team field isn't a sortable field (currently). Another consideration if using the "Look-up issues" action is, it is limited to 100 issues per look-up. Which might…

Hi @Doug Levitt Interesting question. If ORDER By doesn't do it, I'm not sure it can be done. Question: Why does it matter? If you need it to do certain issues prior to others, I would recommend breaking the rule out into 2 (or how ever many you need) and schedule accordingly.

Sounds great!! 

Yes, put {{sprint.id}} into the Sprint field of your rule, for each Story you are creating. As the rule is triggered by Sprint creation, that smart value picks up the ID of the sprint being created.

Hi @Keenan Cassidy What is in the detail of the "Some errors" log entry just prior to your last changes? Also, do you need this rule to respond to another? If not, untick "Allow rule trigger" and about the only other thing I can think of that may improve this would be to actually specify the project (rather then leaving it…

I agree with @Greg Johnson "Releases" being part of "Development" is fair, but it could be argued that creating a Release (Fix version) and monitoring its content is part of "Planning". especially when you consider the multitude of use cases Releases/versions in Jira get adopted for. Also @Josh Sherwood , I like to suggest…

Fair enough @Joe Lagana-Jackson What I've seen done is just using a link type (say dependency) direct to the Initiative from the misc stories. Just a thought.

Hi @Emilio Gómez Can't be done and I'm not convinced it would be a good idea or one Atlassian are likely to pursue. So, in your case I would create a "Project Plan" Epic (or whatever you want to call it) and create your plan tasks in it. From there teams can either; * Manage those tasks from there * Move them (by changing…

I guess you could pull the data into a Confluence page or Jira Dashboard and set it up with the relevant fields as another viewing option for those that want to look. Just a thought.

Only via Advanced roadmaps, which is a Jira Premium feature, so $$