Sam Nadarajan Community Champion

Hello @Nate Dickinson Scrum and Kanban in Jira visualize the same data in different ways through boards. If you'd like to move from Scrum to Kanban, you can create a Kanban board and get rid of the Scrum board. Your project issues would still remain the same. Here's a related question that might be of help.

I'm Atlassian Certified as of Nov 2021 with the following certs: ACP-100, ACP-120, ACP-420, and ACP-620. It was long and hard work, but I keep telling people at my company that the certs were worth it - the exams definitely make you think and I learned quite a bit!

Hello @Zoriana Bogutska_Kolekti Are you talking about your profile name?

Hello @Guilherme Teodoro , I think this documentation will be helpful. Main thing to check is that your customer permissions are not set to open for each of your service projects. Hope this helps

Hello @Marc Blascak In your asset management schema, you'll want to have an Object reference attribute to your employee schema. For example, in my hardware object type, I have an attribute called "User" that is an object reference to the Employee object type: On my employee object type, I have a "Jira User" attribute which…

Hello @SMK - welcome to the Community! Did you set up a context on the custom field to only make it available to a specific project? Have you tried the inverse - going to the screen you want to add the custom field to first then add the custom field from there?

All right, let's take this a little bit at a time - no worries! If you are a project administrator in your project, can you see the "Project Settings" in the left hand navigation of your project? If so, click on that option, then select "People", then can you tell me what roles are currently checked for your user? In…

Hello @Hans , and welcome to the Community! You'll need two things: * A license to Jira Service Management (if you are site administrator or higher you should be able to give yourself a license, otherwise you can ask your site administrator to give you a license) * Project Administrator access in your Jira Service…

Hello @Victor Sandberg - welcome to the Community! I'm not sure I'm understanding the question, each issue has its own issue key as illustrated in your screenshot (EWS-2 v. EWS-4). If you are talking about having a different prefix so it's not 'EWS' for both, then that isn't possible as long as you have different types in…

Hello @Nauman Ahmed this is Automation for Jira, it looks different from what you posted as I can see you're using the server version. In any case, it looks like the Related Issues condition should work if you want to check the existence of an Epic: I understand it will look a little different than what you're seeing, but…

All excellent tips! It's good to revisit these principles in different forms as we all progress through our careers. Sometimes even the mere exchange of information through an online forum as the Community helps us stay innovate and challenge the status quo. Thanks for putting this together! I'm sure a lot of effort went…

Hello @Mélanie Liguet Can you provide a screenshot(s) of what the filter looks like in the JQL view?

Thanks for clarifying, I was going off of memory and jumbled the terms. Can you provide a screenshot of the configuration in the Card Layout as well as a picture of your backlog? Thanks!

Hello Greg, it looks like this question is similar to another one that I responded to. Hope this helps

Hello @Gregory Kremer , TL;DR -> you can't replace the priority field in the backlog but you can add the Severity field Unfortunately, the standard fields that are included by default in the backlog view (issue type, summary, issue key, priority, assignee, status) are not configurable. You can add additional fields if you…

Ah I see - sorry it was frustrating but glad you figured it out and helped the rest of us on here!

Hello @Nauman Ahmed An automation rule structured similar to this may help you. I second @Mark Segall questions and approach, but I'd suggest simplifying the "Epic check" condition as illustrated: As Mark asked, I am not sure how your last rule above plays into this, if that last rule does not depend on the…

Hello @Cameron Loperfido It sounds like the issue layout differs between your issue types. Here's some more information that may help you.

Hello @jeevan , you can try exporting a workflow as mentioned here.

Hello @jeevan and welcome to the Community! You're in the right place, here's some documentation that will guide you in a cloud to cloud migration. Should be pretty straightforward.

Hello @Gabriel Palomarez , and welcome to the Community! You could configure a simple workflow "To Do > In Progress > Review > Waiting" and have the waiting status serve as your holding tank until you're ready to work on it again, then it can move to the To Do process. After some time though the historical comments will…

It looks like the conditions you've put together in the branch rule are the "Issue Fields Condition", you'll want to use the "If/Else Condition". Try that and please share a screenshot of your new configuration and audit log if it still isn't working.

Hello @Kathleen Veach , and welcome to the Community! It sounds like you'll want to use the Advanced Issue Search/JQL to find those issues. In Jira, go to the Issues dropdown in the navigation bar, then select "Advanced Issue Search", then type out your query. You can start by typing "Sprint = XXXX" in the JQL view: You…

What error are you getting in the audit log?

1 - I would add your conditions inside the "For Sub-tasks" branch in your automation rule. You can add conditions inside this branch (hover over somewhere within the branch) and either add a condition or an if/else block which would give you more flexibility. That would cover the first condition, for the second condition…

Hello @Steve Lundy are you an org admin? You should see "org admin" appear right next to your name in the user list. If you aren't, you'll need to contact the org admin on your site. Org admin can only create and manage the sandbox as mentioned here.

Hello @Marcelo Ignacio Cid Abud In your automation rule, I'd consider the following configuration: Trigger: Issue Transitioned (specify to and from statuses at this level) Condition: Specify that you only want to look at non-subtasks (standard issue types) Branch Rule/Related Issues: Subtasks Action: Transition the issue…

Hey! I'm in the same boat as @Dave LIAO - I have yet to see an instance where this has been used in production, but from what I've seen regarding SAFe features and standards it's pretty well "aligned" with that framework.

Hello @Louis Bode - Welcome! When you say "project teams tab in the stories" are you referring to a specific dropdown field? If so, the answer is yes: a Jira Administrator can go to "Jira Administration (settings icon top right) > Issues > Custom Fields" and find the particular field and add an option to it. I'm not sure…

Hello @Ann Rumenapp You may benefit from using a marketplace application such as Projectrak. It would not give you the level of customization you asked in the original question but it would help you track project health. Atlassian is working on a new teamwork directory called Atlas that is currently in beta. It might be…