Comments
-
@Praveen MG You can find the feature request here - https://jira.atlassian.com/browse/JSWCLOUD-10805. The request is in "Future Consideration" Status. So as of now you can implement the workaround suggested there.
-
@jeroen_wilmes 1) What happens with the existing roadmaps in our current Jira standard? Nothing will happens to current roadmaps, these roadmaps will be there during and after the trial. 2) What happens with the the adv. roadmaps if we decide NOT to continue with Adv. roadmaps after the trial? You will loose the access to…
-
@pradeep km You can restrict issue visibility only using issue security levels. You can use some automations i.e. when a component is selected automatically issue security level is selected to that story.
-
@pradeep km You can use issue level security. For eg. security level A for component AA, security level B for component BB etc. And Add necessary users on security levels. Please refer this doc. for information https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html
-
@Fei Xia This may help you https://youtu.be/fWvwkx5_00E
-
@Dan Allenby It seems you should use {{issue.organizations}} instead of {{issue.organization}}
-
@Bala karanam After migrated to cloud instance, user can change email address. Please refer this doc. https://confluence.atlassian.com/cloudkb/change-atlassian-account-email-addresses-969508513.html
-
@Sahrudai Reddy This may help you https://stiltsoft.com/blog/2020/10/how-to-count-lines-of-code-in-bitbucket-to-decide-what-sonarqube-license-you-need/
-
@Tim Cadran You need to edit board filter to sort issues. Please refer this doc. for the same https://support.atlassian.com/jira-software-cloud/docs/configure-filters/
-
@Erica Rodgers Not sure, It may be this bug https://jira.atlassian.com/browse/JSDCLOUD-9491
-
@Erica Rodgers The SLA configuration looks fine, no changes required!
-
@Erica Rodgers As you mentioned in the question "You dont want to include past issues". So here you can mention a date so that this SLA applicable only for those issues created after the specific date. It will be one time configuration.
-
@peter please check manage sprint permission in permission scheme!!
-
@Erica Rodgers You can mention jql as issutype = Support and created >= "2021-12-08". You can change the date as per your usecase.
-
@Lorelle.Deguara In board filter you need to include different projects. If issues are not visible in board then please check column mapping whether all the status are mapped to column or not.
-
Hi, I would like to join this program, please!!
-
@Ngai Chee Weng Please refer this document https://support.atlassian.com/atlassian-account/docs/what-is-an-atlassian-team/
-
@Кирилл Кутузов You have to use workflow conditions. Conditions control whether a transition should be executed by the user. Please find the link for your reference: https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Advancedworkflowconfiguration-conditions
-
@Tien Nguyen It seems workflow changes are in Draft state. You need to publish that, then only changes will reflect.
-
@melina_scholl By default, Jira Service Management agents can: * View Jira Software issues. * Comment on Jira Software issues. * Transition Jira Software issues. Check Browse project permission on Jira Software project , If Browse project permission is set to any logged in users. Then Jira Service management users should…
-
@Helga Tryggvadóttir A subtask is a part of parent issue, not a separate issue. So If an issue is belongs to a team then subtask is also belongs to the same team. So you can't edit the team. If you want to add different team to the subtask then we can't call that as a subtask, you have to create that as a standard issue.
-
@Vivek Patil You can use datacenter trial licenses for testing of these upgrades.
-
@Vivek Patil Recomonded path will be 6.3 -> 6.4.x -> 7.0.x -> 7.13.x -> 8.20.x You migh able to skip some steps like upgrading to 6.4.x. But don't skip 7.0.x upgrade step. Before doing upgrade on production system please try it on Test system. please find the document for your…
-
@Joel Young There is no need of turn on epic progress insights, by default it will be enabled. From the screenshot I can understand you're using story points as "estimation statistics". It seems no tasks/stories in the current sprint have story points. Can you please add value to story point field for your tasks/stories…
-
@Luki1833 You can utilize duedate field. For more info. check this doc. https://support.atlassian.com/jira-software-cloud/docs/schedule-an-issue/
-
@Mel Jensen You can use the JQL query parentEpic = PROJ-100
-
@Lee Burns Similar to Cloud, there is a maximum build time of 120 minutes per step in self hosted runner. It seems parallelization is the way to achieve this. Please find the doc. for the same https://support.atlassian.com/bitbucket-cloud/docs/runners/
-
@Christine Corona WAS operator can be used only with Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields. It can't be used with description field. Please find the doc. link for description field supported…
-
@Joel Young Please check epic link field of current sprint's task/stories. If stories/tasks of current sprint is linked to an epic then you should be able to see the epic progress in insights tab. Please find the doc. for your…
-
Hey @Joel Young Associate the stories/tasks of current sprint to the epic. Then you should be able to see the epic progress in insights tab.
