John Funk Community Champion

Hi Veronika - Welcome to the Atlassian Community! Part of the process (actually step 1) of implementing Atlassian Access is to verify your domain. When that is done, all users in that domain(s) will be considered managed users, even if they are customers. And you should want them to be handled that way anyway if they are…

No, that's where the problem is. https://support.atlassian.com/cloud-automation/docs/limitations-in-team-managed-projects-for-automation-rules/

Hi Abigail - Welcome to the Atlassian Community! That’s fairly involved list of items. Feel free to connect with me on LinkedIn if you would like to discuss in more detail. https://www.linkedin.com/in/john-funk-92261a38

Agents can update the field, but the Reporter will not be able to.

Hi Mario, Can you share the rule with use here? Also, the Assignee field is not a multi-picker field. It is a single user field only. 

Hi Taiwo - Welcome to the Atlassian Community! All issues when created go to the first Status in your workflow. Typically that is the Backlog status. 

Yay! Glad you got it figured out. 

Great! Makes sense.

Hi Henry, I am not aware of what the limit might be, but it is certainly a LOT more than 10. 

Hi Neta - Welcome to the Atlassian Community! Yes, that is one of the strong suits of the Jira product family. They are build on a shared platform so integrating the issues across the projects is very easy. 

It's probably best to go ahead and submit a support request to Atlassian for that. https://support.atlassian.com/contact/#/ Please post back here with the resolution so future readers can see what was needed. Good luck!

Hi @ahutchinson It sounds like IP whitelisting has been enabled for your site, which restricts access based on the IP address accessing it. You should check with your Jira Admin to see what is actually set up. 

Hi Markus, You are not able to do that out of the box with Jira. You can do Issue Level Security, but that applies to only to whether users can see the issue or not. There isn't really a mechanism where one user can see some issues only and update others. The ability to Create or Update are done at the project level. There…

That's what I was afraid of. That functionality does not work with Team-managed projects right now (copying a user field to another user field). 

Hi Samuel - Welcome to the Atlassian Community! Use {{triggerIssue.summary instead of issue.summary

If you hover over the branch, you will see a little popup like in the image below. Click on the copy icon. 

Hi Annapurna - Welcome to the Atlassian Community! The Two Dimensional gadget only works with fields that have a defined set of values like a pick list dropdown or checklist or user picker list. It can't be used with open ended fields like Story Points. 

Yeah, it's not really designed to copy 100 comments - that's excessive. 

"I remember in elementary school a few years back" - thinking that's been more than a few years back @Jimmy Seddon :-)

Hi Izabel - Welcome to the Atlassian Community! What error message are they seeing? Have you tried the Permission Helper in the Permission Scheme? 

Hi Oupa, Have you tried it with an InPrivate Window? Sometimes that reveals if extensions or other items are getting loaded that might be interfering. 

Hey Kate, Not sure on that exact code. But we do something similar to populate a custom Paragraph field with a running list of changes to the field. You could just overwrite the value instead of adding to it each time if you like. 

Hi Simon, We do something similar by creating a custom Paragraph field (multi-line text) and then update it whenever we put something on hold or flag it for some reason. We don't use different date fields for it. Then we add an automation rule to populate it. Here is an example:

Hi Wayne, When you click on it under "My Recent Activity" can you get to the question? Has anyone responded? 

Hi Gemma - Welcome to the Atlassian Community! Can you share an image of your rule here? 

Hi Teresa, Only the fields associated with the Edit screen for the Project and Issue Type should be available for editing, though more fields from the View screen might also be displayed. But only the fields on the Edit screen can be edited. 

Hi Eva - Welcome to the Atlassian Community! Yes, each issue type in Jira can be connected to a different workflow. 

Hi Tumelo, Yes, it is very safe. You will need to install an Atlassian Marketplace app to be a connector between the two though. https://marketplace.atlassian.com/search?hosting=cloud&query=power%20bi

Screens are just a collection of fields - you can't export screens. You can run a filter and then export the results to a CSV field. 

Hi Gauranshi - Welcome to the Atlassian Community! Sure - just use the Defect issue type in the Issue Type Scheme for the project.