John Funk Community Champion

Hi Chinmaya - Welcome to the Atlassian Community! Unfortunately, this is not possible right now. I suggest you vote for this feature request and give it a follow: https://jira.atlassian.com/browse/JWMCLOUD-418

Correct - you can only use Epic Link from Story. And for Epics and above, you will only see issues that are for the Issue Type directly above that issue type. In other words, for Epics, you should only see Bragi Initiative for the parent link field. For Bragi Initiative issue types, you should only see Quarterly Objective…

No directly by most product managers or other Atlassians. This is a community of users. You should open a support ticket with Atlassian if you need/want them to respond directly to you. 

Hi Jakob, Can you share a screen shot of the error message? And of course, the next question is - why so many custom fields? Are these fields just on the form? Or are the mapped to Jira database fields? 

use {{issue.Due date.diff(issue.Start date).days}} Smart values are case sensitive and the field name has to be exactly the same. 

What type of field is Feedback? Number? Text?

Hi Muhammad - Welcome to the Atlassian Community! Yes, you can achieve this with Automation Rules. Create a rule based on a trigger for Issue Transitioned. Select the Status it is transitioning to and then add a new action for Edit Issue. Select the Assignee field and then copy the value from the appropriate custom field. 

Hi @Ivan Andrieiev Can you share a screenshot of the audit log? 

Hi Constantin, If the Affected Services field is a pick list, you should be able to add an Issue Statistics gadget to a dashboard and use that field as the issue statistic. That will give you a count per service.

Hi Vera - can you share some screenshots?

Great! Glad you got it to work.

Can you include a screenshot of the audit log when you run it? That will tell us where it’s failing .

Hi Eloïse, It should not be a problem for text fields. I think the article is more related to if you use a different set of values for a drop down field between the contexts. The value in the text field will not get deleted - it will stay in the field for the issue. It should simply show the values of that field associated…

Hi Shashwini, You would have had to create a new field for a Text type field, because you cannot simply change the type of a field. So you need to use the new field name that was created. 

Great! Glad you got it working.

If you want to hide issues from a user, then you should use Issue Level Security. You are read more here: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Hi Michael, Can you share the actual rule that you have? And what is not working about it?

Glad you figured out a workaround for it. 

Okay, it should show up then. 

Hey @Clay Nichols - Just checking in on this old one. Did you get it solved? 

Hi Alex, You can do this with advanced forms (i.e. Proforma Form). Those don't come natively with Jira Work Management projects though, so you would need to request Atlassian Support to turn that on for your instance so that you can create an advanced form for your JWM project. 

Hey @Mimi Peters - Any rule that runs against a single project has unlimited executions at no cost. It is only rules that run against multiple projects or global rules (no projects identified) that count against your rule limitation. 

Hi James - Welcome to the Atlassian Community! Is this a Team-managed project? Or Company-managed project? And are you sure you Published the workflow? 

Hi Candice - Welcome to the Atlassian Community! First, can you share the rule that you have so far? Next, why are you using a labels field and not just a number field for the numeric value? 

Hi Sujitha - Welcome to the Atlassian Community! Here is what I would do for the rule. Use the trigger for Issue Transitioned to In Progress - but why are you checking all of the statuses it is coming from? Why not simplify the code to just say it transitions to In Progress. Next, change your Condition to say = Empty. This…

So, for rule 1, create the rule with an Issue Created trigger. Then add a Condition for Summary contains Microsoft Then add a new action for Edit issue. Select the fields you describe above and the values that need to be updated. For the Product Categorisation field - what is the field type in Jira? Is it a single pick…

Great! Glad it worked for you. 

What are you wanting to happen when the issue is created and the Summary contains a certain string? What type of field is Product Categorisation? 

I think the count for that is going to be hard. Can you just do a Filter Results gadget and include the Checklist field? 

Hi Parveen, You can create a second board to use with your Jira Work Management project that will give that flexibility if you like. Here is an article that will help guide you in how to do that. https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018