Comments
-
@[deleted] Look at the Board Settings > Columns and see if there is more than one status that is colored green. They may all be in your Done column or you might find them in other columns or in the Unmapped Statuses area.
-
I have been able to replicate the behavior. And I did add the condition after the initial trigger @Bill Sheboy to confirm the triggering issue is a Sub-task. The rule is getting no audit log entries, like it is never being triggered. I confirmed that I had the rule added to the correct project. My workflow is open to allow…
-
Hello @Chuck Do you also have Issue Type as a column for the import data? And what issues types are applied in your example above? When importing, you should map the Issue ID column to the Issue ID field, AND map your Parent ID column to the Parent ID field. You must also make sure that the value in the Issue ID column is…
-
Can you confirm that the automation rule is running when you execute the transition of a sub-task to Done? Are the runs of the rule showing up in the Automation Audit Log? Are there any errors reported in those audit log entries?
-
When last I worked with JIRA Server it was v7.13. At that time, JIRA would not send emails to Groups, but only to Users, because it would only send emails to valid and licenses users. It was not capable at that time of determining if the members of a Group were all valid and licensed users. I think it also did not pull in…
-
Hello @[deleted] Welcome to the community. When you say you are "using jira automation" what exactly do you mean? Are you using the Automation feature to set up a rule to transition the parent issue? If so, please provide the details of the rule you have set up in the Automation feature.
-
I'm not sure if JIRA is able to determine on the fly an issue or request type based on the content of an email, specifically for Service Management. We use only the simplest Service Management configuration at my current company.
-
Hello John, How are you adding the due date to an individual issue, exactly? The updates you need to make depend a great deal on how you are managing your project configurations currently. Are each of your projects using their own Schemes (for Field configuration, Issue types, and Screens), or are you using Schemes that…
-
When you say you need to change the type so they "follow the correct workflows" are you talking about the Workflow/Workflow Schemes that determine how issues can change from one status to another? That is usually linked to the Issue type rather than the Request Type. In that case you would need to be changing the Issue…
-
Hello @Lena Boiser There are two ways that come to mind for how you can do this. If your workflow allows it, transition the issue again from Done to Done (or whatever your closed status is). That will trigger updating the Resolution field. You can do that using the Bulk Change feature. Note, though, that might also update…
-
In your Service Management project go to Project Settings. In the Navigation Pane on the right, about 6 items down, you should see Request Types. Click on that. The screen should show you all the Request Types available for your project. Emailed Request should be only at the bottom and should show "hidden from portal".…
-
Hello @David Mansueto Welcome to the community. Are you using a Scrum board or a kanban board with this project? I don't work with Business projects, but in Software projects viewed with a Kanban board there is an option at the bottom of the Board Settings > General page to change how to age issues from the display, and it…
-
Hello @Praveen Kumar Pandey Can you show us a copy of the filter for the board? Is the filter excluding issues that are in the Statuses you have mapped to the Testing column?
-
Hello @Patrice Champet This is another example of why it is a very bad idea to allow users to delete issues. I strongly recommend that instead of allowing Delete Issue permissions, you modify your workflows to include a new status in the "Done" Status Category specifically for "deleted" issues. If those issues truly must…
-
Hello @Ted To be clear, are you working with a Software Project or a Service Management project? And are you working with a Classic style project or a Next Gen style project? In Classic Service Management projects there is a special field called Request Type which is unique to that type of project. That field is typically…
-
Hello @Ed Hirst Be advised that JIRA does not lock down what can be added to a sprint. There is nothing programmatically that will restrict the sprint to containing issues only that are within scope of the board where the sprint exists. So, you may be getting the message about incomplete issues because some issue has been…
-
Hello @Marcus A Nicholson Are you working with a Classic project or a Next Gen project? Typically, Sub-tasks do not get assigned to a sprint. Instead, the parent issue (story/task) is assigned to the sprint and that brings all the sub-tasks into the sprint.
-
I recommend that you set up a user account to be used exclusively for this integration, and have your 3rd Party use the credentials for that special user/service account. Be advised, though, that special user/service account would need to have access to all the projects where issues need to be created, and the permissions…
-
Hello @Preeti Singh Welcome to the community. That sort of filtering (filter within a filter) is not available in Jira Cloud out of the box. See: https://jira.atlassian.com/browse/JRACLOUD-18918 You will need to look at adding an app to your instance to get that capability. There are a few such apps available like JQL…
-
Hello @John Cherry Are you working with Next Gen or Classic projects? With Classic Projects, you need to ensure that the field is part of the Field Configuration for each type of issues, where those Field Configurations are part of the Field Configuration Scheme assigned to each project. You also need to make sure that the…
-
Hello @Kyle Robinson Welcome to the community. When talking about Service Desk, what is being created for the Reporter is a customer account which is different from other user accounts. Customers have very limited access, only to Service Desk type projects. If you are trying to create issues in a Software project, then the…
-
Hello @Muneer Ahmed Welcome to the community. Are you trying to do a one-time port of Yodiz data to JIRA, or are you trying to link the two applications together, use both, and keep data synchronized between them? JIRA supports importing issues from external sources in a few formats such as CSV and JSON. If you can export…
-
Hello @Dani Gulledge What are the Customer Permission settings for your Service Desk project? And what are the Global Settings for your Jira Service Management configuration?
-
The functionality you are looking for is not currently available. You should contact Atlassian support to get your request added to their backlog.
-
Hello @Sam Peerless Welcome to the community. Can you detail the steps you are going through to add the remote issue link? Also, there is no screen image attached to the post.
-
I've never used that app before, but it seems like this one does something similar on JIRA Cloud. https://marketplace.atlassian.com/apps/1213851/watch-it-for-jira-cloud?hosting=cloud&tab=overview
-
As @Nic Brough -Adaptavist- indicated, you can't just flip a switch to convert the project type. Here is an article about the process for moving from one type to the other: migrate between next-gen and classic projects
-
You're welcome. I did see that I had an error in the update for the filter, though, and you can do it a couple of different ways. First, you want to include the issues where the field is empty, as that would be the default state for the field: ... and (<field> IS empty ...) Second, you can either include the issues where…
-
Have you consulted with that vendor's support team? What are the differences between the projects where TeamBoards works and where it does not work? Does it work for one project type but not another (Classic vs. Next Gen)?
-
Try adding this property on the Closed state (not on the workflow transition): jira.permission.comment=denied