Fazila Ashraf Community Champion

Hi @Madhusudhan Welcome to the community! The given behaviour code works for me. Can you confirm that you are adding this in the behaviour section?

@Alexander Herrler , are the tickets raised through portal or with the 'create issue' option in JIRA? Please refer to similar post in the past https://community.atlassian.com/t5/Jira-Service-Desk-questions/Customers-get-email-notifications-about-internal-comments/qaq-p/1012086 

It shouldn't. You should be able to use the license

@Ezadin Mahmoud , Welcome to the community! It is not possible directly in JIRA out of the box. Only a jira admin can manage custom fields. You could design a custom solution that gets the value from the end user in a JIRA form as a free text field and write a script to add that as a choice to the custom field (script…

@Manoj Somavanshi , you will not be able to upgrade to a version of JIRA which was released after the date your license expired. The migration and the upgrade to a version which was released before your license expiry would work

Congratulations!

@Rohit Suryawanshi , Can you look at the 'Customer permission' and 'Permissions' section and see who has create issue permission in the project? 

@harainye , Is your jira project of category 'Software'? Can you create a new scrum board to check?

Hi @George I think you are looking for this documentation - https://support.atlassian.com/jira-software-cloud/docs/changes-to-issues-in-the-new-issue-view/

@harainye , did you create a board in the project? If someone else created it can you have them checked whether they can still see the board? The creator can check on the permission of the board. You can also create a new scrum board if required

@harainye , can you check whether the project's board is deleted or your permission to the board is removed?

Hi @Julio Cezar Simao (Trimble) This question was already asked in https://community.atlassian.com/t5/Jira-Service-Desk-questions/Service-desk-agent-as-a-default-assignee-for-a-specific/qaq-p/928291 Summarizing, you will need to create a new automation rule which checks the reporter's organization and then assigns the…

@Jason Harwood , glad that it was resolved.. I guess it was some bug in few cloud instances which Atlassian would have fixed quickly.. 

@Carrie Grimes , The completed is the total completed estimates when the sprint ends. If you did not estimate during the start of the sprint, the committed will be impacted and not the completed. Can you look at your sprint report also to see how many tickets were in completed section and their story points?

@Sasha Chernysh , is there any scriptrunner behaviour that hides this field in the screen or action?

@Sasha Chernysh , Can you check the field's context to see whether it is made available for the given project and issue type? Also check on the field configuration scheme whether the field is hidden for the given issue type

Hi @Stuart Longland Could you zoom out in the browser settings and see whether that helps?

@dan , i am seeing other users reporting the same problem. Please raise the bug with Atlassian support in https://support.atlassian.com/ As it impacts many, there should be a high priority on this

@[deleted] , @Gustav Blixt , i am not seeing this issue in my cloud instance but i am seeing other users reporting this -> https://community.atlassian.com/t5/Jira-Software-questions/Epic-Link-not-picking-up-epics/qaq-p/1501171#M101762 Please contact Atlassian Support to see if this could be a bug on certain JIRAs

@Carrie Grimes , the Committed count is the story points of the issues in the sprint during the 'Start sprint' operation. The completed is the total completed estimates when the sprint ends. Can you look at your sprint report also to see how many tickets were in completed section and their story points?

@Jason Harwood , i did find another user reporting the same problem -> https://community.atlassian.com/t5/Jira-Software-questions/Why-is-my-epic-link-field-not-finding-a-match/qaq-p/1501172 When i saw 2 questions with the same problem and tried it out in my JIRA cloud. But It works as expected for me.

@bravedj , if you are interested on returning the stories only, then you should use parentsOf instead of subtasksOf That would return the parents (i.e., stories) where the subtasks are in the given status

@Jason Harwood , can you check whether the epic that is not returned has 'Epic status' as done? https://confluence.atlassian.com/jirasoftwareserver0811/working-with-epic-statuses-1019393039.html

@[deleted] , do check whether the missing epic has the 'Epic status' as 'Done' https://confluence.atlassian.com/jirasoftwareserver0811/working-with-epic-statuses-1019393039.html

Burndown report is only available for Scrum. Not for Kanban.

@Matthias Nickel , Does "issue not in closedsprints() and issue in openSprints()" help?

@Sistemas e Innovación Digital , the move operation doesnt help to move between JIRAs. Instead you could migrate the whole project to the target instance and then move the issues to the target project. If you need a move solution for ad-hoc basis, you can explore commercial jira plugins like Exalate

@Priyanka khare , looks like this question was already asked. Can you check whether the answer in https://community.atlassian.com/t5/Jira-Core-questions/How-do-I-change-the-Sprint-Burndown-Gadget-to-display-by-Issue/qaq-p/440602 helps? Solution: From the Board Settings, go to Estimation * Estimation Statistic = Issue Count…

@Dan King , Can you check your field configuration scheme whether 'labels' set to hidden there?

@Sistemas e Innovación Digital , the information in https://confluence.atlassian.com/confeval/jira-software-evaluator-resources/jira-software-importing-a-project-from-one-cloud-instance-to-another would help You should be able to migrate the classic business project to the target as a classic business project You can…