Curt Holley Community Champion

Hi @Darryl St_ Pierre I'm struggling to understand exactly what you are after, but if you want to do "syncing", "Cloning" of tickets between projects, making them all company managed is going to make that kind of trickery a lot easier. As you have alluded to "The problem is that only the standard fields in the front end…

I think in the edit issue field you want to have {{lookupIssues.Budget Consuption.sum}}

Try these on for size @Rick Westbrock Jira smart values - projects | Cloud automation Cloud | Atlassian Support

@Kerli Loopman have you added the Epic link field to your Alt Epic issue type and used it in the chosen project? Wondering if that might convince the project that there is an issue type at that level and then display the timeline view. Disclaimer, this is just a thought, I haven't tried it as such. 

Wouldn't using Opsgenie be a slicker way to go about escalating to a resolver group/team? Opsgenie could then in turn create an issue in the relevant Project.

Hi @Kevin.Bruce Welcome to the community! Yes, is the answer to your question, though it does depend on filters used on each board and who is assigned. For example, let's say the boards are filtered on the Team[Team] field (in other words Shared teams) and the idea is, if you are in Cloudops Cirrus all work assigned to you…

That's hilarious @Mike - Dreamsuite Consulting I do recall giggling to myself as a child about how certain "To let" signs looked like they were advertising giant toilets (especially when written on a single line and on the side of a commercial building). Ahh, toilet humour. Starts early, never gets old.

Surely the simplest solution here is; Education! Let the people know that following the right stuff in Atlas is the way to ensure you are kept in the loop. Make sure the appropriating linking is in place so that from a Jira issue, they can follow the links and find the Atlas project it is related to.

@jeroen_wilmes the only other thing you have to do to use story points on kanban boards (beyond what @Giovanni Melai has suggested) is say they are actually Scrum boards in the Plan (in Teams/Team settings/Planning style), otherwise AR will not acknowledge the story point field. Which I believe is your problem.

Is it because you have restricted the condition to the "Feature Ideas" project? If the linked issues are in another board, then you need to add them to the scope (i.e. Multi-Projects) in the Rule details session.

You can add smart values in the reporter field. type it and transmit (hit enter)

Hi @Morgan Daly Welcome to the community! To help us try and answer your question, some more questions. * Are you using Jira Cloud, or...? * What kind of project are we talking about JSM? JSW? JWM? * Are you currently using a google form or you are considering that as a next step? * Can you show us your automation rule and…

OK @Sheri Widler I can certainly make suggestions, but if you think one rule is too much maintenance I'm doubtful you will like what comes next. That said, it is true! the issue with these kind of rules is, they do require maintenance. As in, the team members need to be kept current, otherwise the rules just cause…

@Sheri Widler See my screenshot from Feb 23 2022 above. Just use assignee instead of reporter in the condition.

@Chris Your current branch will include both the linked and Sprint squad issues, as you have both Blocks and Is blocked by links in scope. The problem is it depends on how people do the linking. If they are always doing it the one way, work out which way that is and set it up accordingly (i.e. just "is blocked by"). To…

Hi @Adil Bulsara _ADIL_ This is a great example of what can be done: (11) Release CI/CD Deployment through JIRA | LinkedIn But as he points out "We have designed the workflow more structured into our working process. In DevOps Principles we have customized issue types to match the method of project management needs". So,…

Thanks @Kimmi Rawsthorne I've just signed up!

Just detection, alerting...as far as I am aware/can tell. Beacon | Intelligent threat detection for Atlassian products

Hi @Kimmi Rawsthorne These look like a much welcomed option for JSM request types. Question: If an exact match for a field name does exist (say, Employee Location) and it happens to be an Asset object custom field. Would the template use that field or create another one?

Try something like this @Nagarjuna Busireddypally 

Hi @Chris Welcome to the community. All of this should be possible. For 1 & 2 do a rule like this: Trigger: Sprint started Condition: If/Else statement If JQL condition (with JQL to find all the issues in scope and sprint = Active sprint) Then send an email or whatever "A new sprint has begun and your ticket has been…

if you make your branch this, the rest should work.

Hey @Melanie Pasztor If you are on Premium or Enterprise you can control this via Manage product release tracks | Atlassian Support If on standard, then you are at the mercy of an Agile SaaS product and the release schedule they choose.

Hi @Jonno Katahanas I signed up for early access when i was still in Vegas for Team23, but have not heard back. I presume that means I missed the 200 cut? That said, i now have it in a One Atlassian site, but Smart Sections do not appear to be present yet. Is that right?? When are they likely to be in-place?

BTW @Nagarjuna Busireddypally could you accept my initial answer, so as to help confirm that it solved the issue and help inform others in the community. Cheers!!

As mark point out here When story point in epic is updated, it should upd... (atlassian.com) your branch needs to be getting the Parent Link from the issue (in this case, the Epic)

Hi @Nagarjuna Busireddypally It will go much like this Solved: How do you sum up story points to the epic using j... (atlassian.com) But taking it up a level so that the 1st condition is Type = Epic and the branch will need to point at the Portfolio Epic

Hi @Maria Del Rosario Gonzalez Options I've seen work affectively are: * Used a "committed" label, then have filters showing Committed, but not completed. Committed and completed etc. * Have an Objective issue type and the teams set Objectives and commit to them (linking out to one or multiple features/epics or whatever…

I don't think @Vikrant Yadav solution is what you are after @Nagarjuna Busireddypally as you want to populate the hieratical children, not the linked issues. I would go about like this. Trigger: Field (Team) has been edited Condition: and Team is not empty Branch: by JQL issue in…

Repeat the branch process, but this use either Sub-tasks or Stories (or other issues in Epic) depending on which of those two scenarios is the case. Then you'll need to add the two together and average them. So you will likely need another field to store the child based data in, then put the 2 together.