Thorsten Letschert [Decadis AG] Community Champion

Hi @Yoann Pascali , Choosing "Projects" from the admin menu in the top bar (the cog icon) should lead you to %yourBaseURL%/secure/project/BrowseProjects.jspa?s=view_projects, which lists all the projects available on your instance, regardless of whether you have "Browse projects" permission. Regards, Thorsten

Hi @Simon Webb , It seems like Ashish was already able to guide you with his well-documented step-by-step-answer.

Great insights. And a +1 for your 'Trust Warning' section.

Hi @Simon Webb , What type of custom field are you trying to add? Regards, Thorsten

Hey @SAzaruddin.mp , For company-managed projects, a valid workaround without additional apps is * not having the field of interest on the edit screen * adding the field of interest on a transition screen * have a global reflexive transition (from any status to itself,) adding the transition screen with your field of…

Hey @satyanarayana_singamsetti , While this sounds tricky with out-of-the-box features, here are two suggestions if using a 3rd party app is an option for you: * Bulk management of versions (https://decadis-apps.atlassian.net/wiki/x/wsSIiw) is one of the dozens of handy admin-focused features within Admin Toolbox for Jira…

Welcome @Amir Tavakoli , Seems like we share a passion for workflows. Looking forward to your input!

I like the quick filter approach, a good intermediate solution between blocking upfront and automatically (or unattended) removing issues. It draws attention to those issues and leaves it up to the user to decide whether to add the estimate or remove the issue from the sprint.

HI @srikanth_rao , AFAIK there is no easy answer to your question (yet). A corresponding feature request is being tracked here: https://jira.atlassian.com/browse/JSWCLOUD-15376 However, depending on your setup, you might want to give the following workaround a try: * You've stated that making estimated required globally…

Hi @Ashley Li , While JQL autosuggest won't work anymore, you can run the query with reporter = %accountID% To get the ID, * head over to https://admin.atlassian.com/ * go to Directory > Users * filter for "Deactivated" * click on the user of interest The ID is then shown as the last part of the URL, e.g.,…

I'm glad to hear you've been able to solve your problem. As stated within the other comment, please consider accepting the answer(s) - especially the one including the detailed workaround above.

Hi @Swati Verma , The problem described here sounds similar to yours, speaking of the "user picker (People) type" regarding the custom field of interest: https://jira.atlassian.com/browse/AUTO-421 The link includes a workaround that might fit you! Regards from Germany, Thorsten

Hi @Jannis , You're more than welcome! In case no one else is able to provide an actual "fix" to your problem, I'd appreciate it if you marked the answer as a solution.

Hey @Jannis , I've just jumped into a site in order to check your request. My observations: * In general, every user can select his/her own homepage via 'Personal Settings' (%yourSite%.atlassian.net/jira/settings/personal/general) - and choose between 'Your work', 'Projects directory' and 'Dashboards'. * Changing this…

Hey @Nicole Baumeler , Admittedly, I don't have a solution with out-of-the-box functionalities. However, I would happily show you a solution if an additional app is an option.

Hi @satyanarayana_singamsetti , The order should be editable via the "Advanced Settings" (%yourBaseURL%/secure/admin/AdvancedApplicationProperties.jspa) - scroll down to the jira.view.issue.links.sort.order property there. Customizing columns is not available afaik. There are several closed tickets over time,…

Addition: While I was checking the easiest way to remove the wrong issue type, "Story (migrated)", I saw that the "Delete Issue Type" now comes with a "Migrate Issues" button. That being said, the first and second steps mentioned above might be replaced by heading over to your issue type settings…

Hi @srikanth_rao , And a warm welcome to the Community! To fix your issues, you might want to * Make sure your "correct" issue type "Story" is still available in all the relevant projects. * Run a search for the wrongly associated issues, e.g. type = "Story (migrated)" * Select "Bulk change" from the meatball menu in the…

Hi @G.W. Swicord , Click on your avatar in the upper right, go to "Manage settings" > "Notifications" tab > "Settings" button and look for the "Badges I earn" option in the "Frequency" section. Cheers, Thorsten

Hey @Nicole Baumeler , Thanks for your responses. Does it necessarily have to be your proposed "first ticket acts as a parent, following tickets should be subtasks" approach, or is issue linking also an option? I was playing around a bit with your scenario, but unfortunately, I have not succeeded (yet?). While I currently…

Hi @Alon Yehezkel , If I understand your requirement correctly, this should work, removing your first "Linked issues match" condition. In your screenshot, there's an AND between the two, and an issue can't be of type "task" AND type "T3_Bug" simultaneously. Within the branch, assuming your BIP ticket is returned within the…

Additional hint: You might want to consider limiting the scope of the rule to "Multiple projects" and only selecting the "triggering" projects of interest to avoid unnecessary executions with regard to automation limits.

Hi @Alon Yehezkel I'd suggest the following approach: * Adjust to your initial query, e.g., check for the issue type "T3_Bug" so that the rule only advances for your issues of interest. In your scenario, that might pass for ONB-152. * You're already correctly switching within the branch to the linked issues. In your…

Hey @Alon Yehezkel , Welcome to the Atlassian Community! Could you please share some additional information that might help suggest the best answer? * You're explicitly stating that this question is related to a parent. Are sub-tasks involved? If so, is the status of those sub-tasks also affecting the mechanism you're…

Hey @Nicole Baumeler , Sounds like an interesting use case. Before being able to suggest an actual solution, I have some additional questions upfront: * Are we talking about DC or Cloud? * Are your "PRTG Alerts" received via email channel? * How is the relationship towards "system XYZ" determined, e.g. the email address, a…

Great overview. I'd like to add the option to create additional "Labels" custom fields that can then be restricted to specific projects, e.g., to be used within specific teams. Of course, the stumbling blocks remain, but I have found that it is easier to establish a consistent nomenclature within smaller groups, such as…

While the view now includes "Required fields are marked with an asterisk *" it seems like - at least for now - this asterisk isn't shown anywhere, even when using the built-in "Field Required Validator". Paired with the result of https://jira.atlassian.com/browse/JRACLOUD-76479 I'm not quite sure how this fits together? *…

Great session! Investigating permissions looks neat.

Hey @christopher.branaman, I hope you don't mind me stepping in on this: yes, the result would include all issues linked to the Epic, regardless of their projects. Cheers, Thorsten

Just voted, @Britta Neugebauer _yasoon_ - now I expect you to bring these cards to the next event!