Marc -Devoteam- Community Champion

Hi @Rhishavdas K I suggested to re-export and try importing again. I would suggest if that doesn't work to contact Atlassian support and reference the following Jira ticket. CONFCLOUD-76197 I see that you are on a free plan in Cloud, this will not allow you to reach Atlassian Support. A work around for this it to temporary…

Hi @Manish Kumar Welcome to the community. If all admins are out of the organisation, you will reach out to Atlassian. Atlassian Support

Hi @Helen Platt The default period "done" issues are shown in a plan is 30 days. As I see on the screenshot of your sprint the sprint is like 10 weeks. Check the plan settings as mentioned by @Ste Wright 

Hi @Rasajna Meka I can list some, but why, as automation is an integrated part of your subscription. apps come at an extra cost. You could look at scriptrunner. But as I said why, as there is a default option in your Jira!

Hi @Cabby There are now riks, it depends on your WoW. We usually use the 3 ,month guideline, but issues related for support we use a yearly epic. So even in a single project you can differentiate in time. But the guideline as a development company the best practice is to use the 3 month period.

So on the issue are you set as the Cross Pod Approver? Are there any conditions or validators the transition "ALL" to status "Deployment Rejected" or the transition "Cross POD Approved" and what about the "auto transition" transition Because the last transition is not in the approval and could cause the issue not approving…

Hi @Rasajna Meka This is not an opportunity without automation or another app that has posibilities to do this.

HI @Jelena Pavić Looking at your screenshot, I think you haven't used the free products for some time. Atlassian disables them, you should have received emails on this. To have them re-enabled, you wil need to contact Atlassian, this can be only via support. As a free user you are not eligible for support. As a work around…

What are the details on the approval step of the POD LEAD status approval and are there also any validators or conditions on any transitions incoming or outgoing form that status?

Hi @Dmitry Aleshkovskiy Can you show some details of your configuration? As I'm reading your issue, you use JSM and you don't have Jira Software? JSM now offers a kanban like board option, but this can have swimlanes. If you do have Jira software, you can have a kanban board with your JSM issue on the board, but where are…

I would look at the workflow to see what the setting on the approval step are.

Hi @Alexander Ziegltrum Currently this is not possible. The only workaround is the use the smart values in automation to mention a user and individually add all members of the team. See the following issues open at Atlassian: * AUTO-166 * JRACLOUD-80134 

Hi @Mohamed Saad Taha You can't as the number is also derived from a filter. From the Rich Filter add-on diocumentation: View Permission The View Permission allows you to browse the rich filter and see its configuration, to use it in gadgets and to see the results it returns. A rich filter is available to all users who can…

Hi @Adam Witek You api post shoul look like this: { "fields": { "project": { "key": "REST" }, "summary": "Issue created from REST API", "issuetype": { "id": "1" }, "customfield_10300": { "value": "Mammal", "child": { "value": "Elephant" } } } }

Hi @Manmohan Anand Are you also a member of the role Service Desk Team (are you an agent). This as you can be an admin on the project, but if you don't have this default role, you can't approve or excute any action on project issues

Hi @Patrick Till Could you be kind to share the full automation rule and all it's details. This will help us in the community, to maybe give you a solution based upon your rule. What is the condition used and it's settings.

Hi @Mohamed Saad Taha You can't to view any information from a dashboard users need browse permissions. This is ootb. What add-on are you referring to and does the documentation of the add-on provide any options, otherwise the above still applies

Hi @cheikh charles ndiaye Depending if you are on server or cloud. On Cloud then solution given by @Sharumathy Krishnan is your only option. The first steps to be added are: - Delete all issues from the project - Delete the project - Delete the project from trash But as I see you probably are on server, you could delete…

Hi @klaudia.brysiewicz Welcome to the community. The user can be in Jira and granted permissions on projects, but the user has no license assigned. This is why the 403 occurs. The user might have had license before, but probably an admin has revoked the license for this user.

Hi @Alexis Lamrani I get this, but No the chart can't be adjusted regarding you need.

Hi @Johan Karlsson I think the image you show is about the JSM status translations for request. These are set on the request configuration. Go to the project settings of you JSM project and to Request types, select you request and see workflow statuses. Let me know if this was the case or that I'm not correct.

Hi @David Morns If it's only this one, you project or Jira admin could also trigger a re-index on the project in relation to xray, to see if this solves the issue. See https://docs.getxray.app/display/XRAYCLOUD/Project+Settings%3A+Re-Indexing 

Hi @harry.michel.ntamen Welcome to the community. To simply answer your question, No you can't. Multiline field is set to 32,767 characters in Cloud - and is not editable. You can vote for this to become configurable via JRACLOUD-63007 There are also no Marketplace plugins available to solve this issue.

HI @AutomationUIUser What kind of fields are you missing? Fields from apps, these are not available via the Jira API, as they are not part of the API. They might be available from the APP API, if there is one.

Hi @David Morns Welcome to the community. It could be that you don't have the right permissions anymore, that looks like it to me. This on the statement that other colleagues don't have issues. Check with you project admin or Jira admin if there have been changes (if you're not an admin yourself). Xray offers permissions…

Hi @Alexis Lamrani This is not how the concept of jira and SCrum works. A sprint has a certain capacity of work, set by the scrum team. Issues in a sprint are estimated to a number of story points, this should not be over the team limit set. This also means that the sprint capacity should be defined per person, but as the…

Hi @Natalia Mojica Use the scheduled trigger. This trigger runs on your schedule set and then checks. Execute your JQL in the scheduled trigger and add a comment if JQL applies Example rule:

Hi @Princess Dagala As @Tim Kopperud mentioned this option is bit available, see referenced Atlassian documentation that he mentioned. Try: created >= 2023-06-01 AND created <= 2023-12-31 AND project in (TA20, BC526, SOTF, OM, COR, CE, CMTP, HEL, HP, SW, WMS) AND issuetype = Bug and linkedIssueType is EMPTY

Hi @[deleted] Currently no, the only option is the work around you described. There is an open issue at Atlassian for this: JRACLOUD-40477 

Hi @Madhura Lodam It might be that you are running into the issue that relates to using the same named issue type in Team and Company managed issue types. See: https://jira.atlassian.com/browse/JRACLOUD-75176 IT might, otherwise check that the issue of the types you want to make are on the project AK