John Funk Community Champion

Hi Andrew - Welcome to the Atlassian Community! Jira is designed to follow standard Agile practices, whether they be Scrum or Kanban. But also the tool is customizable to meet the needs of those implementing the tool. If you are trying to learn Agile practices by learning the tool, that's kind of a backwards way to do it.…

Hi @_lluis5847 Check the Permission Scheme to see who has the Transition Issues permissions. Also check to see if there are any validators on the transition. 

Hola Albert, El cronograma está disponible con Jira Work Management, no con Jira Software.

Well, I know mine works, so there is something in yours not right. haha. I suggest logging out the values for the fields before you do the summation to see what the values of the fields are. 

@Vish Reddy {Revyz} 

Hi Svetlin, Maybe try adding some validators for the fields in the Create transition of the workflow.

Hi Dd, I don't know a way of creating the sub-tasks via loop. I think you will have to include a separate action for each one in the rule to create them.

Awesome! So happy to hear!

By design, changing things in this view will only affect this project. 

Hi Ray - Welcome to the Atlassian Community! Another option is to create a second board if you have Jira Software also installed. This article will guide you through the process. https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

Hi Nenad, I am not completely following your problem. Request Forms are not new - they have been around from the beginning. If you do not want the field on the Request Form, simply remove it. Can you give is more specific details of the problem you are encountering? 

Hi Vansh, The Severity field is probably marked Required in the Field Configuration used by the project.

Okay, thanks. And that's what I figured was the problem. Change the All of the following conditions drop down to the Any of the following conditions option. Be sure to publish the changed workflow. 

Yes, that will work as well. But labels are harder to deal with. A simple radio button with yes/no options works really well. And just hide the field from the screen. 

Me either @Johanna Pichotka_APTIS_ - good for you!!

Hi Taha, This is one I use that works. You should be able to simply edit the field - and use sum instead of average like in my example. Also, I would change over to Parent instead of Epic Link since that has been deprecated. 

Hi Allie, Are you using the standard approval process built in to JSM to determine UAT Approve or Fail? If so, one option might be to have an interim status before the Approve/Fail status. You can have the same transition names - Approve or Fail, but then add a transition screen to the Fail transition that includes fields…

You might need to clear your cache for your browser. Or try another browser and see what it looks like there. 

Hi Sudakshina - welcome to the Atlassian Community! The Description field is not available to use in JQL for determining updates. But you can do this a couple of ways. 1. Create an automation rule to email you when the field changes. 2. Create a custom date field that is hidden from the screen, then create an automation…

Hi Rakshita, Not exactly sure of your question, but Team-managed projects by design are to be completely independent of all other projects. So if you are trying to clone something from one project to another, that's probably why it is not available like it is for Company-managed projects. If you need that functionality,…

Hi Sanjivani, You can have separate Edit and View screens. Leave the field on the View screen and remove it from the Edit screen. Then create a self-looping transition on the status with Conditions that allow only certain people to execute the transition. Then add a transition screen with the field on the screen to the…

Hi Muhammad, You should be able to create an Automation Rule based on an Issue Transitioned trigger (to Done). Then add an action for Edit Issue, select the multi-select field, then place each of the values in the field. 

Hi @锐 王 - Welcome to the Atlassian Community! You are not going to get that with out of the box Jira. Maybe with an add-on app. Your problem is figuring out: 1. if those fields change 2. when You are not going to be able to do that with the JQL you have.

You are welcome.

Hi Angus - what Conditions are on the transition that regular users can’t see?

Unfortunately, no I don't. Nor do I believe that I have that kind of permissions. @Monique vdB 

You would need to change the filter that that board is using. Or create Swimlanes for each Priority

Well, you would think that Due date is getting updated for the issue therefore, take the timeline out of it, it should still shows the value in the Due date field. You definitely need Atlassian to explain that one. Please post back here with the resolution. 

That still makes absolutely no sense to me, but hey, knock yourself out with it. You will need an automation rule that has a trigger of Issue Transitioned. Use the two statuses for To Do and In Progress. Then add a Condition for Issue Type = status-a Then add a Branch for Parent Under the branch add an action for…

What do you mean by there no response? What did you do and what happened?