Jack Brickey Expert

It may not be global but just a project specific one.

Thanks for the update @Janice . One question, when Kudos first rolled out it was auto-enabled for all which drew quite a bit of backlash resulting in an opt-in solution. Is there an easy opt-out process? 

Hi @Sam Smith , I suspect that someone has set up an automation rule that causes this behavior. In fact, it is a common request of other community members to have the parent follow the child. As a result, the typical suggestion is to create an automation rule to do just that. I would check under project settings/automation…

Customers should not be able to add new organizations via the portal share button. Are you finding differently? Only administrators or agents? If so, configured or allowed to add organizations. Customers can only find existing organizations if they are a member of those organizations.

Use a filter like this... project = abc and Sprint in openSprints()

So what exactly is your share goal? What do you want customers to be able to share and what do you want to prevent? If you want to prevent sharing then you need to not use Organizations. How are you using Organizations today if not to silo customer sharing?

Hi @Jimmy Tracey , the first thing to do is to set up Customer Permissions to best align with you project. Note that customers can only see/share within the Organization(s) they belong to.

Thanks for the clarification @Thomas Schöpping indeed. I see you are using TMP projects and yes the behavior is different between the default filters and custom filters. I can't say why this has been implemented this way. You may wish to provide feedback to Atlassian via the in-app feedback link (under the "?" Icon) or, if…

Hi @Thomas Schöpping , welcome to the community. Could you provide more details on the type of project you are referencing here. I just did a quick check in my team managed project and custom filters in both the backlog and the board view work the same way. Specifically custom fields work in an "And" manner. Feel free to…

Hi @Sanskriti Pathak , welcome to the Community. Have a look at the two-dimensional gadget in the Dashboard. You could set the Sprint field to the X-axis and assignee to the Y-axis.

Hi @kate.berlova , welcome to the Community. Indeed fields added to the layout will appear in 'line 2' of each issue. There isn't a means of adding as a column. 

Hi @Jagadeesh Chander , unsure if it is different in DC but in Cloud you can access Audit Logs here - settings/apps and under Scriptrunner in the sidebar.

You may find this useful as well - configure-the-site-homepage 

Hi @Michael Thorpe , by default home page do you mean the page that appears when you click Home button? Can you share an image of what you want to change exactly?

Hi @Sameer Mohamed , if a label is being added as part of the corrective action, then you can use that same label to skip the transition. Specifically add a condition that includes labels != "my label"

Hi @Sarah Isaacs , please share how you are setting the Assignee in each case (task, subtask). The following works fine for me. For the Task create I used the following smartvalue. You need to replace "sub-assignee" with your custom field name. IMPORTANT: The custom field type needs to be People type.…

Indeed this is simply a limit on advance booking time.

Hi @Ntamen kamogne harry Michel , please share the source of this info.

Hi @Bobin Johnson , you can Reopen a sprint which will return all issue from the sprint to the backlog. Note any issues defined in the completed sprint that were not completed that happen to be in a current active sprint will remain in the active sprint. please see this article - Reopen Sprint

Hi @kim hs ,are you trying to report a performance issue? If so please contact Atlassian Support.

Hi @[deleted] , it would be best if you could provide a screenshot of your automation rule as well as the audit log when the issue triggers assuming it does in fact trigger. With that said, do you want to make sure that you use the following to update your custom field. action: edit issue, and select your custom field to…

Yes if you are using company managed projects. example.... "my special drop-down" = "this value" will return all issues regardless of project where the drop-down field "my special drop-down" has a value of "this value".

Hi @Ovadia.Dan , unfortunately, there is not such a function within any native gadgets. You would have to look to third-party add-on options for that level of flexibility. 

Are you sure that field does not exist in other projects or maybe as a CMP custom field? Can you run a query for all issues using each variant and report findings?

Hi @andylee . in this situation here is what I do: * rename one of the dups so it is discernible from the other custom field. Example change one to "First Name DUP". * Run a query for all issues where: "First Name DUP" is not EMPTY. You will want to copy the contents of First Name DUP in each issue to the "First Name"…

Hi @Sarah Isaacs , Thank you for all of the details that certainly helps. The first thing I observe, is that for your assign issue action you need to be sure that you are referencing the new subtask not the issue associated with the trigger. I think you simply want to set the Assignee as part of the issue creat action.…

Understand. Unfortunately the component lead approach just isn't going to work at least through automation. I guess that whenever they change the component lead, they will have to do a JQL search for all issues with that component and perform a bulk update.

Ok so looking back at your OP you state "...but the field is not a custom field". If not a custom field what is it? You must've created a custom field that the user can select from drop-down, right? Would you mind providing an image of your automation rule. Also what does the audit log tell you when you try to run the rule.

My proposal is to not use the Component field at all but rather create a custom field 'zone'. You might even consider a cascading field (though not required) where the first level is the Zone and the second level is the zone lead. The second level would be a single value always and default to the value. example: zone >…

Given what you have conveyed I would not use Components but rather a custom field "zone" and automation to assign/reassign based on that field being updated.