Comments
-
Hello @Ebru Ergenc Take a look at my answer on this post: https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-find-out-if-Issue-was-created-via-Jira-WM/qaq-p/2278098 When a JWM issue is created by submitting a form, a special label should be getting added to the issue. If you need to add another label, you…
-
Hello @george.laskowsky Welcome to the Atlassian community. Are these issues in a Team Managed project or a Company Manage project? You can get that Type information from the View All Projects page under the Projects menu. It is not possible to customize which fields display for issues in the Child Issues section. Whether…
-
Hello @Donald Collins Welcome to the Atlassian community. Access to delete issues is based on the Role to which the user is assigned in the project. I see in the lower left corner of your image that you are using a Team Managed project. The Project Administrators for that project can adjust the permissions allocated to…
-
Hello @Brandon Ruetsch Welcome to the Atlassian community. You could accomplish that with Automation Rules. https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ Automation Rules can be created by Jira Admins. Those Admins might also have given the permission to create automation rules to others, like…
-
Hello @Glen Brannigan Do you want the prevent the transition from being available if there is not a Fix Versions value, or do you want to give the user an opportunity to enter a Fix Version value while making the transition and prevent the transition if a value was not already present and they don't enter one? For the…
-
Hello Lili, Issues linked to what? Are you trying to retrieve not just the child issues of the Epic, but also the issues linked to those child issues? If you change the output display from Details to List, you can add the Linked Issues field to the output columns. For each issue you retrieve that column will then show the…
-
@Patrik Cipriano Welcome to the Atlassian community. Have you opened a support case directly with Atlassian?
-
@Michael.Sly The View All Issues page is not something that has to be activated. It is available by default under the Filters menu in Jira Cloud. That is the page from which general issue search filters can be created and executed. It is also where end users have been able to access the Bulk Upload from CSV option. @Matt…
-
Hello @Kira McCoan Welcome to the Atlassian community. Can you double check the Type of the base project by viewing that information in the View All Projects page under the Projects menu, and confirm that it shows there as Service Management vs. Team-managed Service Management?
-
Hello @Munir Patel With the For Each option I don't believe it is possible to dictate the order in which the sub-tasks are cloned and added to the previously created issue. I think that you could instead use a Lookup Issues action to retrieve a sorted list of the sub-tasks of the original issue, and then use a branch to…
-
The Lookup Issues action will retrieve issues only from the projects you have specified in the Rule Details for the Scope of the rule. I see that your rule has a multiple projects scope. You will need to look at the details of the projects in scope and determine if projects are missing from the scope.
-
Correct. That is the design for the native burndown report.
-
The way the filter is written 1. You will get all issues from the OPTAMAP project 2. Plus you will get the direct child issues of the Epics you called out, regardless of what project they are in. 3. You will not get the subtasks under the child issues of those Epics, unless the child issue and subtasks are in the OPTAMAP…
-
Please show us your current rule with the details of each step.
-
Hello @Munir Patel The user can use the current Clone Issue function to clone the issue and it's subtasks in the same project. They can then use the Move function to move the parent task to the other project. And then the user can associate the moved issue to a different Epic You could potentially build an Automation Rule…
-
Hello @joy.martins Welcome to the Atlassian community! To create two boards that show issues for just one team each you will have to use something in each issue to identify the team that owns the issue. That could be a Label, or a Component, or the Team field, or another custom selection list field. There really is no way…
-
You may need to be an organization admin to add users to the product. It depends on how the administrators have configured the environment. Based on the message the user is receiving, the admins have already been notified. There is not a method for non-admins to get the name of the Organization Admins. I recommend that you…
-
You need to use the fields that have been specified in the plan as the fields used for start and end dates. This can be customized in the plan, so you need to check the plan settings to find out which fields are being used.
-
The error you received suggests that there may have been an error in how you wrote the JQL. Can you share the actual JQL statement you used?
-
Hello @Jorge Bejarano Welcome to the Atlassian community! With what type of project are you working? You can get that information from the View All Projects page under the Projects menu. Are you working with a scrum board or a Kanban board? Can you provide a screen image of what you see?
-
Hello @Ayush Pathak With native functionality you can define context for a field per project and issue type. You can't define it per screen. Can you provide more information about your use case? Is this for a single issue type in a single project? If so why would you want different values based on the screen for that issue…
-
Hello @Phyoe Tay Zar Minn Welcome to the Atlassian community! With the native functionality the only way for a burn down chart to show progress is for the end status to be in the right most column. You would need "development completed" and all the subsequent statuses to be mapped to the right most column for the board…
-
Hello @Richard Welcome to the Atlassian community! What is the Tye of your project? You can get that information from the View All Projects page under the Projects menu. There is a native Category field that is applicable to Business/Work Management projects. In that type of project you add values to the list by simply…
-
Hello @Jamie Young Can you provide more information? Can you outline your use case, or the problem you are trying to solve? What is your specific question on this topic?
-
Hello @Denis Droz No, that is not a configurable option. And Atlassian has declined past request to either make it configurable or increase the limit. Can you describe you use case for needing more option? Perhaps we can suggest an alternative.
-
Hello @Andy Bailey If your customers are going to be licensed user of the Jira Software project, and you are giving them Browse permission for that project, then you can use Issue Security features to limit the customers to see only a subset of issues in the project. The specific Issue Security options depend on the type…
-
Hello @Navyasri Yedlapalli Welcome to the Atlassian community! If you downgrade the archived projects will remain archived. You can access the archive and restore archived projects. You will not be able to archive additional projects. Refer to https://support.atlassian.com/jira-cloud-administration/docs/archive-a-project/
-
Hello @AJ McCraw The first question you need to answer is do you really have more than one sprint or do you have a single sprint being used by two teams? Go to the View All Issues screen under the Filters menu. Search for all the issues in the affected sprint using the "sprint=" criteria. After the = start typing in the…
-
Hello @pernille Welcome to the Atlassian community! With a Team Managed project you can specify default text for the Description field. That is not supported for Company Managed projects with native Jira functionality. It could be possible with a third party apps. There is a work around for Company Managed projects. It…
-
It worked for all the native HTML macros that were in the specified instance.