John Funk Community Champion

One other test - have you tried using the account id instead of the username? Or maybe the full email address?

The board simply follows a filter for should show up on the board. So you can simply use the JQL in your board filter in the rule. 

Hi Chris - Welcome to the Atlassian Community! You don't need the fields part in the middle. Just {{issue.summary}}

Fair enough. Is it only with this one user that you are having the problem? Can you upload with other users? Does the user have Assignable User permissions in the Permission Scheme for this Project? 

Great idea!!!

Okay, but I still don't see why you don't just create the issue in Jira instead of adding it to a spreadsheet. You can export/download the list of issues from Jira if you want/need to look at them in a spreadsheet for some reason. You are still typing in all of the data, whether it is is an spreadsheet or a Jira issue.…

Mine is pretty much any kind of cookies. I am especially fond of Snickerdoodles and peanut butter cookies with a Hersey Kiss in the middle. Also, ginger snaps/gingerbread cookies. But the cookies need to be chewy and not hard or too crunchy. :-)

This is a good description and should work for you. 

Hi @Dionei Piazza - Did you ever get this solved?

Hello and Welcome, Ganesh! We are glad you are here!!

Hi Sudesh - Welcome to the Atlassian Community! You need to insure that the Context for each of those fields is available to the Issue Type that you are moving to. Go to Settings > Issues > Custom Fields Search for the field and then click the 3 dots menu on the right side. Select Context and default value

Go to Project Settings for the Project Then Workflows Then click on the Switch Scheme button and select the new Workflow Scheme. 

Have your run this rule? Did it work for you? If not, what was the error or result? Can you share the Audit Log? 

Hi Aynura, Yes this is possible. But realize that the resolved field is already capturing that date. Sometimes you can use resolved or resolveddate in your filters. See if you see that first, but you could also still set the date. To set the date, create an Automation Rule for the Issue Transitioned trigger to Done. Then…

Hi Mayuri - Welcome to the Atlassian Community! First, it is always better to post a brand new question than to add a question to an existing post, because only the couple of people on the post will see it versus dozens otherwise. Workflows remain in an inactive status until the workflow scheme they are attached to are…

Just curious but why is all of this work being done in spreadsheets and not directly created in Jira? 

Tal vez sea el momento de enviar un ticket de soporte a Atlassian: https://support.atlassian.com/contact/#/

Hi Jon, Jira use a complex method of sorting issues on a board. If you have the ORDER by rank added to your board filter, this will allow you to move cards up and down inside the Column/Swimlane. It also use that default method of sorting. Upfront, I have no idea of the mechanics and exact algorithms used. However, my…

Ashish - can you share the value you see in the drop down for Link Types? Does this link type already exist? 

Hi Santhosh - Welcome to the Atlassian Community! You can achieve this with an Automation For Jira rule. If you are not familiar with that tool, here is some more information: There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month * Project: In all versions, you get…

Thanks for jumping in Petter!

Hi Chris, Go to Project Settings on the project. Then choose Request Types When you get a list of the Request Type, click on the Portal Groups link in the top paragraph. When you get to the Portal Settings page, click on the Portal groups tab. Then click on the dropdown for the Request type. Then remove the Request from…

Hey Shelley, As a quick fix, I would just upload the issues with your name. Then once those issues are created, do a Bulk change and Edit the issues to update with the new user name. 

No, that is not possible in Cloud version. And there are no add-ons. 

Hi Ashish - This appears to be a duplicate post of this one: https://community.atlassian.com/t5/Jira-Software-questions/Update-custom-field-based-on-linked-issues/qaq-p/1558421 Is that correct? 

Hi Sergey, Yes, all access to projects are controlled by the Permission Scheme for that project. For access to products, then that is controlled by groups. So you can remove the user from the Jira Service Desk Users group (and Customers group if you have that) and that should take out access to the product. 

Hey Steve, What I would do is start by creating a common Issue Type Scheme that has the issue types that you want to use on a project. Then go to the project settings for each project one at a time and compare what is already there with the new. If they line up or the new one is better than the existing, then simply…

Can you share a screenshot of what you have? Maybe use the custom field id, too, like this: { "fields": { "assignee": {{issue.customfeild_16999. accountId}} ] } } Where 16999 is replaced with the id for your custom field. 

Did you follow the guidance in the link I sent? For Simplified workflows the the Project Administrator actually modifies it through the board settings. 

Hey Chris - sorry, just now getting back to this. No, the Summary is basically the card title. But the Description is where you can put lots of text. The Summary is a single line text field and the Description is a multi-line field. Thanks @Dirk Ronsmans for jumping in and adding clarity!