John Funk Community Champion

Hi @Manoranjith - You should not be adding Epics to a Sprint. That is not standard Agile functionality. 

That looks like it is either Jira Work Management project (Business type) or maybe a Team-managed project. 

Custom fields with selectable values must be hardcoded. 

Hi Ada - Welcome to the Atlassian Community! You could add another status between the initial one and the one that has the Escalate this issue transition. You could create an automation rule that transitions the issue to this in between status after 3 days if you like. 

Hi Rahul Edit the workflow to add a post function to all transitions going from a Done type status to any open Status. In that post function you should choose Clear Field Value and click Add Then choose the Resolution field and click Add Be sure to Publish the workflow. To get rid of current values: Add a new self looping…

Okay, so the JSM issue is created and you have an automation rule that creates a JSW issue. Correct? And you are having trouble linking those tickets when you create the JSW ticket? Can you share the rule that you have so far? 

Hi Lisa - Welcome to the Atlassian Community! There's nothing really magical about the setup- if you is not what you like you can easily change it for the project you create. Just go to the Project Settings > Summary Click on the Issue Type Scheme name When you get to the scheme, click the Actions menu on the right and…

Hi Emanuel - welcome to the Atlassian Community! You cannot change a custom field type - you must create a new custom field and then migrate any data from the first field to the new field. 

Hi Cindy, Maybe the rule is getting triggered as the result of a different rule? Can you check the Rule details to see if the box is check for Allow rule trigger?

Hola, Jacqueline: los campos bloqueados son campos del sistema que no se pueden cambiar. ¿Qué campo está tratando de cambiar y por qué?

Hi Rachana, You cannot make any field have dynamic values. For cascading, you can have a value in the first field and different values in the second field based on the value in the first field. But you can't have different/dynamic values in the first field depending on other fields. What is your exact scenario that you are…

Hi @Admin OKZT - Welcome to the Atlassian Community! You can handle this a couple of ways. But you start both in the same place. While on the Board, click the 3 dots menu in the upper right and select Board Settings. Click on the General menu option if not there already. Easiest (for Kanban board, not Scrum board) - scroll…

Sorry I don't as I don't actually use the tool. 

Hi @Jojin - It is better to create a new question so that more people can see it and can provide answers tailored to your needs. Feel free to tag me on it if you want. But quickly, yes, what you have will only allow the Current Assignee or Reporter and any Project Administrators to see any issues on the project. 

Okay - can you give me a step-by-step of what you are trying to do and what you want to happen when? 

Welcome Laurie! Let us know what you like and don't like about what you see. 

Hi Elle - Welcome to that Atlassian Community! Can you provide some more information? What type of project are you using? Company-managed? Team-managed? Jira Work Management/Business? What type of board are you using? Built-in board that came with the project? Scrum Board? Kanban board? 

Hi @Sehrish Gul Just ran across this post. Since no one had responded, that's a pretty good indication this is not available. You should open a support request to Atlassian to have that capability. 

Great! Glad you got it sorted out. 

So, is your problem solved? I noticed that you accepted the other answer. 

Hi Darren, I see nothing wrong with your rule. What is the value of the Third Part Support that it is passing through? Can you share the audit log for that issue? And are you sure that the issue is not getting changed to something other than Microsoft after it runs? Can you check the history of the issue? 

Great! Glad we got it solved for you. :-)

Is this a Team-managed project? And if so, yes! If it is a Company-managed project, you wouldn't even be able to edit the field type. 

That shouldn't matter. Did you create a new field? What is it called? Maybe try to test it with the Reporter field. 

And are you using any add-ons related to this?

Okay, try this in the Due Date field: {{issue.created.plusDays(2)}}

Can you include a screenshot of exactly where you are using this?

Yes, even if there is just one value - it doesn't like that it is a multi-user field in general. Jira is fussy like that sometimes. :-)

Not for the history, no. Maybe using an API, but not sure. The other thing is that you can create a filter that returns the issue that you want - might be as simple as Key = ABC-123 Save that filter and then create a Dashboard or use an existing one and add a Gadget to it for Activity Stream. Then use the Filter you…

Squad Leader is a multi-user field? And it works? Or it is a single user field and works and Reviewer is a multi-user field? I suspect the second statement which is why that's not working - it doesn't know which one to get.