John Funk Community Champion

Hi Miheaela - Welcome to the Atlassian Community! It says it is working - that's not an error. Did it complete? What happens if you click on Refresh? 

Great! Thanks for that. Can you share a screen shot of the General Details of the rule for the second one that is not firing? 

I don't know if they can do them directly from Slack - but thinking probably not. Yes, you would need to add the user to the Approvers field. You can set it up so that they get an email and can click on the Approve or Decline buttons in the email directly and not have to log in. 

Hi @Kelly Arrey - I can do it with Company-managed projects, also.

Hi Sebastian, Sorry, but I am not understanding your question. Thank you for sharing the screenshots - very helpful! But what is happening that shouldn't? Or should happen that is not happening? 

Hi Javeria - Welcome to the Atlassian Community! Can you provide some more information? Is that a custom field you created? Have you added the field to the screen? What type of project are you using? Company-managed? Team-managed? Is there a Context associated with the field? 

Understood, but that is currently not available. 

Hi Paul - Welcome to the Atlassian Community! Yes, someone with the ability to see the ticket can be setup to be an approver of the ticket. 

Sí, ese es un campo del sistema y muchas otras funciones se basan en ese campo. Por lo tanto, no se le debe permitir cambiar su estructura. Sin embargo, ciertamente puede cambiar los valores en el campo.

Thanks for sharing. What do it you want it do do differently than what it is doing?

Hi Akash, When you modify your workflow the last step will be to migrate your current issues in those statuses to any of the remaining statuses. So, when you publish the workflow, you must move your issues out of any status that is getting deleted (it will guide you). 

Well, now that I have moved to the Middle East, it is 100F with heat index of 122F today. (38C and 50C). And though I am completely free to sit outside if I like, I am happily sitting inside with the air conditioning. :-)

Hi Amey - Welcome to the Atlassian Community! Here is some more guidance for this, but it might be because you don't have the Make Bulk Changes global permissions under Settings > System > Global permissions. https://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/

Hi Nikolaos - Welcome to the Atlassian Community! Can you share some screen shots and more details? 

Hi Aleksei, What type of project are you using? Company-managed? Team-managed? Business/JWM? I am not able to reproduce the problem with a workflow used by Company-managed projects. 

Hi Mark, Correct - with the Free version, every user has access to everything. Therefore project roles have no affect on anything - so there is no reason to add people or put them in roles. The purpose of the roles is to control permissions and access. But since everyone has access with the Free version, then they turn off…

Hi @AisM I am not sure how the board technically operates that allows that to happen, but obviously it does as I have also noticed that functionality in the past. Is there something in particular you are trying to accomplish by knowing that? 

I really think something is jacked up with your instance. {{now}} should work. https://confluence.atlassian.com/automation/jira-smart-values-date-and-time-993924864.html I would go ahead and submit a support ticket with Atlassian. https://support.atlassian.com/contact/#/

See if you can set it to {{now}} when it is created. And if that works, then add an Edit Issue after that first update to use: {{issue.duedate.plusDays(2)}}

Hi Zacharoula, So the other fields have values in them? But for the same issue just these fields don't? If so, try these: {{issue.Epic Name}} {{issue.priority.name}} {{issue.customfield_10063.value}}

Hi @mayurpandya1993 This will give you a good overview: https://www.atlassian.com/software/jira/service-management

You are welcome. Let us know how it goes. 

Hi Afrin - Welcome to the Atlassian Community! Click on the Search box in the upper right in the top nav bar. Then click on Boards Search for the board and then click the 3 dots menu on the right. Select Delete.

Hi Andrea, Yes, you can do that. While on one of the issues, click on the Configure gear on the bottom right. You will need to be an Administrator to do that. This will take you to the Issue Layout screen. There you can move fields into and out of the other areas. Description fields area is the one in the central view area…

Yep, that should work. 

Yes, only a Jira Administrator can make that change. 

I don't think there are any. You might try the Marketplace app ScriptRunner Behaviours - but not sure if they support those custom fields yet. 

Hi Shivani, In a Free subscription, you can't. And in a paid subscription, you can't really either. You can remove them from the Browse Projects permission, but they could come in through Project Settings and add themselves back in if they want. It becomes more of an education process at this point. 

Not unless you create a Team-managed project. :-) It is not available like that for Company-managed. 

Great! Glad you got it sorted out.