John Funk Community Champion

Hi Phil - you need to show the full Context for the custom field - not the Field Configuration. Go to Settings > Issues > Custom fields Search for the field, click the 2 dots menu to the right and select Contexts and Default Value. Also, make sure all of those fields are on the Create screen used by the Sub-task issue type…

Hi Suneeta, Can you share the rule that you have and the exact error you get? 

Hey @Max Black Did you ever get this solved? 

Hi Lucas - Welcome to the Atlassian Community! No, you will not be able to hide that. 

Hey @Miles Kwon - Did you ever get this solved? 

Hi Vasiliy - Welcome to the Atlassian Community! No, that is not possible. The user would need to click on the blue Create button. It's still just one click - whether they click the + button or click the Create button. 

Sure, that should be possible. You need to link the issues when you create the JWM project. Just make that another step in your rule that clones the issue. Then you can create another rule based on the issue transitioning in the JWM project. Then you would add a Branch for Linked Issues. And then a new action under this…

Hi Sofia, System fields are pretty straight forward: Issue Type - issuetype Summary - summary Attachment - attachment Description - description

Hi Erik, If the rule is not even getting triggered, you need to check the box in the Rule details for Allow rule trigger. Save and publish and then give it another try. 

Hi Nikita - Welcome to the Atlassian Community! Add an Automation rule to update the new custom field (probably when the issue is created) Add an Action for Edit Issue In the new custom field put this: {{issue.key}} - {{issue.summary}}

Hi Geetha, You can see this article to help you with that - but you will need to use Automation (there is no good reason not to use that which I am aware of). 

Hi Kim, You should open a support ticket with Atlassian to see if the user's email address has been blacklisted for some reason. https://support.atlassian.com/contact/#/

Hi @Bruno Altenhofen - Any more feedback? 

Ah, since you are moving to Data Center, then Jira Service Management is going to be your best bet. You can have some very robust forms with that. You might also be able to use the Issue Collector. https://confluence.atlassian.com/adminjiraserver/using-the-issue-collector-938847338.html

Hi @N McMahon If you run the filter and see the issues, but then with the same filter you do not see on the board, then there are a couple of things to check. 1. Make sure that the statuses that contain the issues are mapped to a column on the board. 2. Check the sub-filter at the bottom of the Board settings General tab…

Hi Nirav, Yes, this is easily doable. Who is the Actor you are using for the Automation rule? That actor would need to have access to the Jira Software projects you want to create an issue for. You might just use Automation for Jira as the Actor - that should solve that as long as the atlassian-addons role or group is in…

Ha! Not sure how pink I am - or healthy for that matter. :-) I don't work for Atlassian, so not sure that I can offer much advice there. Maybe concentrate on a particular product and learn it really well. Also, get a certification in the same area. 

Hi Valerie, I guess the simple answer would be to not allow a value of 0.

Hey Bob, I would suggest: https://marketplace.atlassian.com/apps/1228694/revyz-backup-restore?tab=overview&hosting=cloud

Hi Ranjan, Try using statusCategory != Done to show all issues not in a Done type status.

You are welcome. 

Hi Zekai, One way to do it might be to remove the priority field from the Edit screen. Then create a self looping transition on the status in the workflow (a transition that starts on a status and ends on the same status). Then add a transition screen to the transition that includes the Priority field and the field you…

Hi @Raghuveer Madhu - Do you still have questions about this? 

Hi Aleksandr, Here's an article that will help guide you on how to create a second board: https://community.atlassian.com/t5/Agile-articles/Creating-a-Second-Agile-Board-for-Team-Managed-or-JIra-Work/ba-p/2115018

And to add to Valerie's answer - it will depend on with they are Company-managed versus Team-managed. And you can so do issue links between issues if you need something on a common level like Epic to Epic or Task to Task. 

Hi Ranjan - Welcome to the Atlassian Community! It looks like you have a comma that doesn't need to be there. Delete that and give it a try. You might also want to change the triggerissue to triggerIssue as the smart values are also case sensitive. 

Hello and Welcome, Sukant!

No, you will not be able to do that. As I mentioned, how Atlassian does rank is very complicated as it is used across the platform and multiple boards. 

I think you are only asking for trouble doing that. Either HR wants to be a part of the solution or not. I would escalate that upwards if they don't. There's no reason for that type of siloed behavior in my opinion. I would expend your energy on that versus trying to work around them. 

Great! Glad it helps.