John Funk Community Champion

Hi Johnson, Can you share the details of what you have in the Edit issue for the fields you are updating? Maybe try something like: {{issue.issuelinks.outwardIssue.summary}} If that doesn't work, the try inwardIssue instead of outwardIssue.

You said from yesterday morning that it wasn't working. Was it working before? What changes did you make? Did you add new Field Configurations? Did you update those Field Configurations to include the Description? 

Congrats to the Rising Stars! We are glad you are here!!

Hi Venkat, I am not aware of a way to restrict who can put users in the Approvers field in a dynamic way like that. You might be able to with the ScriptRunner Behaviours app, but wouldn't have a lot of hope for that right now. 

Hi @Mark Macayan - Welcome to the Atlassian Community! Click on the search box in the upper right in the top nav bar. Then select Boards in the bottom of the popup. Then click on the Create Board button.

Hi Jeremy - Welcome to the Atlassian Community! No, the user displaying the dashboard must be a valid user and one who consumes a license. We actually created a service account in Jira and use that for displaying dashboards in a public environment on a wall-mounted TV. But it does consume a license. 

Hi @Abir Brahem - Were you able to validate Mark's suggestion? I am going to mark his answer as accepted, but let us know if you still have questions. 

Hi Ife - Welcome to the Atlassian Community! Have tried doing a Move on it first? 

Tentatively planning a meetup in Dubai in mid-September and another one during GITEX in October. Come visit!

Hi Lin - Welcome to the Atlassian Community! For user picker fields in Jira you will need to supply the email address of the user or their Jira username (if you know it). You can't just stick a person's name in there - it has to be a valid user. 

Your default group is usually just the jira-users group. 

Gotcha - You should be able to create some automation rules to create all of the issues up front and even do the links for Blocked by, etc. 

We started with Labels and quickly learned that was not the route for use with all of the misspellings, case sensitive considerations, etc. So we switched to Components and were very happy with those. It brought a lot of structure for us and commonality in reporting. 

Hey Alex, I would say that makes sense as Assets (as implemented in the tool) don't really apply to projects - they apply to the organization. 

Very good - whatever works!

Hi Chad - Welcome to the Atlassian Community! You can create an automaton rule that will do that for you. Here is an example:

Hi Shubham, Can you share some screen shots? 

Hi Louise - Welcome to the Atlassian Community! It's probably because the Resolution field is not getting cleared. You need to update your Workflow for the transitions from Done to the open statuses to add a Post Function to clear the Resolution field. 

Born in the USA but now living in Dubai, UAE

Hi Dushyant, So the same issue was showing one thing for the Description of the field yesterday and today for the same issue it is showing something else? 

True, the user would need a Jira Software license. I need to update the article to include that. Thanks for pointing that out!

Great! Glad it is working for you now. 

Or you can modify the Permission Scheme to add project roles and then just place the users in roles on the other projects that have access to the Work on Issues. This is definitely more straightforward and a better long term solution. 

Hi Christian - Welcome to the Atlassian Community! You cannot hide full columns with the quick filters - only the issues. Your filters will be based on the status(s) used by the column. For example status in ("In Progress", "On Hold", "Testing") would only show issues in those statuses (you would replace with whatever the…

Hi @Mee Soo - Welcome to the Atlassian Community! Can you share your rule, and then what you are trying to do? 

Hi Trevor, Make sure you are a Project Administrator in the Project Role as well. It is looking for that versus whether you are a system level administrator. 

Hi @John Zakaria - I am marking Jack's answer as Accepted as it should have done the trick for you. Let us know if you still have questions. 

This article should help guide you. :-) https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

Hi Sascha, You cannot change the type of a Project. You have to create a new project with the type you want and then migrate the existing data to the new project. 

Hi Nathalia, You are lucky if this is the first time you have encountered this. :-) But you will need to copy the current workflow and then make changes to the new, inactive workflow. Then you will need to edit the Workflow Scheme used by your project to Add a workflow (this new one) and replace the existing workflow by…