Comments
-
Hi Nodar, We use a Marketplace add-on called Azure AD Attributes. With that app it is easy to retrieve the Manager of the user. https://marketplace.atlassian.com/apps/1220477/azure-ad-attributes-for-jira?tab=overview&hosting=cloud
-
Hi Suyash, Take a look at this sample rule in the Automation Playground. https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/9919294
-
Hi Valentin, I think you meant Reporter in your question details and not for them to work on the issues. Try adding the user as a Customer on the project (entering their email as the user).
-
Hi Daridan, Check the Permission Scheme associated with the project to make sure you have the Link Issues permission.
-
No, not if your objective is to let users see issues on a dashboard that they are not allowed to see by Issue Security.
-
Ah, I forgot you were doing this through the API. So if you add the field back to the Edit screen, then the API works? If so, that's just what you will have to do. And yes, I would create another tab called System or something like that. People are less likely to click on it then.
-
Oh, take the Backlog status out of Todo and put it to the far right under Unmapped Statuses. You have a built in backlog because it is a Scrum board and you do not need to map that.
-
Hi Vasilis, Check the Permission Scheme associated with the project to make sure you have the Link Issues permission.
-
Hi Solak, Versions are project specific and cannot be shared across multiple projects.
-
Hi Nagarjuna, Please see this previous post about setting the Team field. https://community.atlassian.com/t5/Jira-articles/Automation-Set-your-Advanced-Roadmaps-Team-automatically-when/ba-p/1761588
-
Please share the rule that you have created and what is not working with it.
-
Hi Valentino, What type of project is this? If Company-managed, you can add the text to the default value for the Description field. However, I would not do that!! The reason being that it would apply to all projects in your Jira instance, and I am sure you do not want that. Instead, create a custom field that you will…
-
Hi Moshe - you should be able to leave it on the Create screen, but remove it from the other screens.
-
So, did you see the Portal Customers option in the path I took you through? That should be a menu option on the left side.
-
They are the ones who will need to do something. Let me see if someone can come here.
-
Hi Fabian, What type of project are you using? Company-managed? Team-managed? And are you sure you are using a Scrum board? And where do you have the Backlog status mapped to? Can you share some screenshots?
-
Hey Marc, Are all of the fields number fields? If yes, I would set the default value for each field to 0. And then bulk change all existing values to 0 if they are empty. Finally, and I don't know if it really makes a difference or not, but remove .fields. from the code for each field so that it is only: {{#=}}{{issue.API…
-
Thanks for the clarification. Did you remove the user from the project per the KB article? And if so, are you looking for something else to be done? Another option is to go to Settings > User Management then select Products in the top nav bar. Next click the three dots menu to the right of Jira Service Management and…
-
Okay, will see if someone from Atlassian can come visit here.
-
Okay sorry, I should have explained more. I didn't have a custom field in the playground that was a yes/no field so I used the Resolution field. Just replace the resolution field with your yes/no field and change the the value in the first to No. And for the Else change from Resolution to your yes/no field and change the…
-
Hi @KITSCH AND BOLD - Welcome to the Atlassian Community! Are you receiving any emails from Atlassian at all? Or just not from that project? If not at all, then we will need to have someone from Atlassian look at your email address to see it if has been blocked for some reason.
-
Hi Vighnesh, The problem is that you probably have multiple transitions to the various statuses all using the same name or similar (Move to Done). Check the workflow and the transition name for going to each status and rename them to be more descriptive - like Mark as Rejected, Mark as Accepted, Mark as Won't Do, etc.…
-
Hi Benjamin - Welcome to that Atlassian Community! You are not able to change permissions or drop users like that in a Free instance. Let me see if someone from Atlassian can provide you better guidance.
-
Sure see below:
-
Okay, thanks, but I don't know what a "unity" project is. Can yo describe that more? Or show a screen shot of the project? And how are you trying to create the issue? By what method?
-
Hi Alvaro - Welcome to the Atlassian Community! Is this a Marketplace app? If so, you should contact that vendor directly for assistance.
-
For 1. you will probably just have to ask around to see who created the group and why they did it. There's not a good way in Cloud to see all of the places that a group is being used. It would be really nice if you good. You might be able to attempt that through the API, but that is beyond my capabilities. Depending on how…
-
So it sounds like there is maybe issue level security applied to the project? Because if the filter itself returns multiple issues but a single user only sees a portion of those issues using the same filter, then there has to be extra security applied to it. Using the dashboard won't override that.
-
Hi Gajanan, You should be able to create a rule based on a Field Value Changed trigger. Then add an IF/ELSE condition block where you handle each of your scenarios above. Under each Else section add a new action to Comment on Issue.
-
You have covered the gamete so far! Is there another animal that you would like to try?