Comments
-
Olá, É um projeto gerenciado pela empresa ou um projeto gerenciado pela equipe? Se for um projeto gerenciado pela empresa, você pode criar um novo projeto com a mesma configuração marcando a caixa "Compartilhar configuração" durante a criação do projeto. Quando você fizer isso, ambos os projetos usarão os mesmos esquemas…
-
If this is an Issue in a Company Managed project you need to view the issue and find the field "Epic Link" in that issue, then edit the content of that field.
-
Hello @Luc Witters (Altrad Services BNL) Are these issues in a Company Managed project? If so, there is a Permission called "Modify Reporter" in the Permission Schemes for Company Managed project. You need to have that permission in order to modify the Reporter field.
-
Can you provide a link to a video where you see that? I have not seen that capability in the Basic Roadmaps feature that is available with the Standard subscription.
-
@Nic Brough -Adaptavist- 's answer works for issue in a Company Managed project. If you issues are in a Team Managed project there are a couple of options. 1. In the Backlog screen click on the lozenge for the Epic in the issue card. That will give you the option to select a different Epic parent or unlink the issue from…
-
Hello @Steve Rapaport If you are talking about the Teams that are created under the People menu, there is currently no way to use those Teams in filters nor in fields in issues. Here is a change request concerning that on which you can comment and vote. https://jira.atlassian.com/browse/JRACLOUD-74842
-
In a Team Managed project you have to go to the existing issue and click Add Epic in the breadcrumbs at the top. That will allow you to select an existing Epic to which you want to add the existing issue as a child. Alternately on a Backlog screen that has the Epics panel displayed, you can drag an issue from the issue…
-
Hello @Jason McNamara Welcome to the community. Can you clarify how you created "View A" and "View B"? Are those quick filters on Board A or are they entirely separate boards based off of their own Saved Filters? If the latter, sprints will display in the Roadmap only if the sprint was created in the Board to which the…
-
What was the API call that you executed?
-
Is this for a Team Managed project or a Company Managed project? Is this a Software project? Is it a Scrum board or a Kanban board? For a Scrum board, per the documentation https://support.atlassian.com/jira-software-cloud/docs/what-is-the-roadmap/ "Child issues in Scrum projects are scheduled using the dates of the…
-
Hello @Colleen The display of the time stamp for when the Comment was added should be getting adjusted for the time zone preference specified in your Account Profile. There may be a default time zone specified for your Jira instance, but you can change that to match your local timezone in your profile. If it is displaying…
-
Hola, Debe especificar un Estado para la transición al que existe en su flujo de trabajo para ese tipo de problema en ese proyecto. Si el estado que ha seleccionado no forma parte del flujo de trabajo, el mensaje de error que recibe es legítimo. La regla de automatización no puede hacer la transición del problema a un…
-
Hello @Dolly Kirubavathi Can you possible provide a screen image of that? I think what you have done is used the generic Issue Linking functionality to create the link between the issue and the Epic. That is not typically how child issues are associated to a parent Epic. See here in this screen image of an Epic there is a…
-
I have not worked specifically with the Discovery product, but if you are using the generic issue importing functionality available to import issues to any type of project, then yes, you can import more issues without affecting the ones that are already present.
-
Did you intend to attach a screen image? Please provide the steps you are executing. How many issues are you attempting to edit at one time? How many fields are you editing at once? What do you mean exactly by the changes are not sticking? What specific fields are you trying to edit and what values are you changing from…
-
If the issues you are retrieving are not child issues of an Epic then the field will be blank. You would need to go to those issues individually and add them to the appropriate Epic and then the field will be populated.
-
Your rule indicates you are editing two fields; "SLA Due Date" and "Advanced". What is the "Advanced" field? The error message in the log is referencing customfield_10153. What is that field? Is that the "Advanced" field? This is what the Log Action action needs to look like to log the value to the rule Audit Log.
-
Hello @Dolly Kirubavathi For issues in a Company Managed project the field "Epic Link" hold the Epic issue key for the Epic that is the parent of a given issue. For issues in a Team Managed project the "Parent" field holds the Epic issue key for the Epic that is the parent of a given issue.
-
Hello @[deleted] Welcome to the community. There are a variety of third party apps that could be used to synchronize information between two separate Jira instances. Here is a search from the Atlassian Marketplace to help you get started.…
-
Adding to @Nic Brough -Adaptavist- 's comments... You said you may need to give access to a few admins per client. If you want people who are currently Customers only to access and interact with the data in Software projects, you will have to grant those individuals licensed access to your Jira Software product. Are you…
-
How do you know which Epics you need to "work with"? Are the Epics assigned to you? You can adde multiple Epics to the criteria for the Epic Link field and get all the child issues for all Epics at once. You can also add Epic Link as a column to the output so that you tell which child issues belong to which Epic.
-
Hello @bryce ready I am working with a Jira Cloud Free subscription and I have not been able to replicate your experience so far. When I go into a Team Managed project to edit the workflow this are my steps: 1. Click Project Settings 2. Click Issue Types 3. Select the issue that has the workflow with the transition…
-
Hello @ryan.zore is customfield_10153 the Date Picker field to which you are trying to assign a value? Have you used the Log Action action to see what value you actually get when you use {{now.plusDays(14)}} ? Can you show us the entire rule and the details of the component where you are trying to assign the value?
-
Hello @Evan Reeves Yes, that is a possibility. Each Automation Rule has an Actor setting which specifies the identity under which that rule will run. The specified Actor needs to have appropriate permissions in the target project(s) to execute the actions specified in the Rule.
-
Hello @Shane Parkinson If you are using the "Create Linked Issue" option that shows in the Linked Issues section of the parent issue, it is true that it will not automatically link to the issue you started from... unless you have included the Linked Issues field in your Create Issue dialog. Within the Create Issue dialog…
-
There are a few ways to accomplish that goal. One is to create the custom field and set it using an Automation Rule that looks at the other two fields and determines how to set the new field. How often would you want that check to be executed? At what point in the issue lifecycle do you require the Due Date or Estimated…
-
An alternative to using an Automation Rule is to set up a Saved Filter, share the filter, and have each user subscribe to it to receive one email with all the issues assigned to them that are due. In that case you would want to add to your filter this criteria: AND assignee=currentUser()
-
Also, you do not need to have both the JQL in the Schedule trigger and the LookUp Issues action. Use one or the other, not both.
-
Hello @Jason Yeung You set the permissions for users for a Project using the Permissions Scheme. Using the Permissions Scheme you can specify that users have read-only permissions by granting the users only the Browse Permission. Permissions can be granted to Project Roles and to User Groups, so you could group the users…
-
I'm still working out how to run this scenario with a Lookup Issues action, but I do have it working for a Schedule Trigger with a JQL. The following sends one email per issue to the Assignee.