Marc -Devoteam- Community Champion

Hi @Vidya VASUDEVAN No this can't be done, unless your issue types are like this. Epic -> Epic Feature -> Level 1 story level Requirement -> Level 2 sub-task level With Jira ootb on project level, there can't be a level placed between Epic and Level 1 issues (Story, Task, Bug, etc...) Otherwise this can only be achieved by…

Hi @Josef Sigl Please share the details on your created rule, with step details and also with the audit log failure details. What type of custom fields are you using, share details. All this information will help community members to assist you with your current request.

Hi @Kenisha Naidoo Specify the project in the "Create" action and uncheck JQL in "Scheduled" trigger. Don't use "Same project" option.

Hi @Hallaien I have never user this call myself, as I'm not on DC. But I think this is better to to with Postman or Open API.

Hola @Sandra Perez Si, tienes que tener un plugin de pago.

Hi @Sandesh TM Look at the issue and the API documentation, how to setup the call. If you can't figure it out, then respond here. The option is available, try to make that call this will give you insight how it works. Just getting a handed answer will not teach you or make you understand the workings. I don't have time…

Hi @Franz Wallisch So all works except, issuekey IN updatedBy("*","2024-11-11","2024-11-14") AND cf[10086] ~ "K*" This could be simply valid as you want to find issues in an updated range by anyone and the custom text field should start with K If there is no issue in the time frame matching this, no results will be given.…

Hi @Gal Fatal This can't be done. You have the workflow option or the option in the general settings to disallow unassigned issues on global level. Or use a 3rd party app JSU, see making-assignee-field-required-when-allow-unassigned-issues-is-turned-on-in-general-configuration 

Hi @Andrei Eleodor Sirbu Yes, this I can replicate on my side as well. This seems like a Bug. I suggest to raise this at Atlassian Support, to have them check this as well an to confirm this as a bug.

Hi @Franz Wallisch On my instance and other instance I manage, this provides results. How does you API call looks like, does issuekey IN updatedBy("*","2024-11-11","2024-11-14") give results in GUI?

Hi @Franz Wallisch Welcome to the community. Please use issuekey IN updatedBy("*","2024-11-11","2024-11-11") Double quotes need to be set.

Hi @Gittel Marcus Suspend operation can be performed for both managed and unmanaged users. Once a user is suspended, they can't access the site from which they were suspended but can log in and access other sites. The suspended users aren't counted for billing. So this also means no options to be a reporter of receive…

Hi @Seenivasan K If using Opsgenie now in Cloud, you will need to use the Team option from the main menu bar. In a Team you can configure Opsgenie, in the feature options on a JSM project Incdent Management needs to be enabled.

Hi @Sandesh TM This should be possible on updating an issue, see related topic on Atlassian Jira JRASERVER-34423 

Hi @Nico As stated in the referenced community post, this would require a 3rd party marketplace app. The automations suggested are good, but Yes time logged could be longer, depended the time the issue would have been in statuses before In Progress.

Hi @Lance Li Sorry, but then I would sat just announce it again, based on change reason, instead of trying to set a complex workaround that is bound to fail some time and you will also get complaints.

Hi @Arnau Barbecho Barrado Then use the trigger "multiple issue events" and use the options Issue Created and Issue Updated. Then based on issue creation the the priority is determined and if an agent updates the issue, the rule could then trigger again and the priority is determined based on the same rule, but based on…

HI @Jochen Betz Raise it with Atlassian Support. And explain your issue. I can't replicate the issue you are having

Hi @scutrell To update page options, will never update JQL filters. You could use filter on a single page with option like resolved >= startOfMonth("-3") and resolved < endOfMonth("-1") this will always show the last 3 months. This will always show the last 3 months resolved issues. JQL has by default no startOfQuarter and…

Hi @[deleted] Quick filters don't add issues to a board, they are for filtering issues that are on the board, based on the boards filter. On the new board, in the top right corner, select the 3 dots and select configure board. In the "General" section , you see the board filter specified, this filter decides what issues…

Hi @yosi hatem As @Bill Sheboy mentions why, looking into the system will give you this information. Why start mailing this, get stakeholders involved in the system and not via email.

Hi @Florent Plomb Also check the instance global audit log, as mentioned by @Bill Sheboy 

Hi @[deleted] This is because team management projects have a single board and no other boards can be added to the project. You can create a board on company managed project containing in team managed projects issues.

HI @Raj Branch on Epic (parent). See documentation, branch-automation-rules-to-perform-actions-on-related-issues Epic Link is not an option, this is text, not an issue

HI @Anastasiia Roshchupkina Welcome to the community. Check out the documentation on PDF export, customize-exports-to-pdf 

Hi @Caroline SCENI This might be that some pages are still based on the old Confluence editor. You might need to convert these pages first. From documentation: "Atlassian Intelligence will generate a summary of changes since you last visited the page or post." AI has no permission options, its available based on enablement…

Hi @scutrell What are the filters you are using, between fixed dates or else?

Hi @Andrei Eleodor Sirbu I tried this in multiple plans on multiple instances and I'm not able to duplicate this in any of them. Do you have this in other plans or only in this plan? Can you try an incognito window in your browser or another browser and is your browser up to date?

Hi @Joni Johnson There are no options to create general (global) configurations within Atlas. Also there are no feature request or bugs relating to this, see Atlassian ATLAS 

HI @J P This seems like a valid proposition. To have favorite views in a plan, be starring them like boards, filters, etc.. Currently there is no such an option and I did't spot anything in the Cloud Roadmap on this. You could raise a feature request via https://jira.atlassian.com/secure/Dashboard.jspa