Comments
-
Hello @Jacob Goodroe Have you confirmed that the values you have provided in the CSV are values that are available in the respective fields, through the UI?
-
Do your HR people need to view the tickets like a customer would, through the customer portal, or do you want them to have Service Desk Team member access? If the latter, you won't be able to restrict their view based on component value. They will be able to see all tickets in the service desk project. If the former then I…
-
No this is currently not possible. Refer to this post https://community.atlassian.com/t5/Jira-Service-Desk-questions/Controlling-Customer-Access-Across-Multiple-Service-Desks/qaq-p/1025003
-
Another user had asked a similar question. Take a look at this post to see if it provides any useful info for your scenario. https://community.atlassian.com/t5/Jira-Service-Desk-questions/Communication-with-client-is-not-working/qaq-p/1412485
-
@Chima Abah No, unfortunately you cannot populate the options in a Custom Field definition through CSV import. The CSV import is for creating and updating issues in projects. Entering and updating issues through the UI would not allow you to add new values to a Single Select Custom Field, so you won't be able to do it…
-
Exactly what did you do to make the "Time Tracking" field mandatory? Did you change the Field Configuration to make "Log Work" required instead of optional? Or are you using a Validator in the workflow transition for closing the issue to ensure the field is not empty?
-
Hello @Jacob Goodroe Welcome to the community. What type of fields are these custom fields? Can you provide a small sample of the CSV file with these rejected values?
-
Export what report, exactly? There are many reports that can be obtained and exported. Depending on what exactly you are trying to report, there may not be any need for a "parent" project. There may be an easy way to generate the report once incorporating data from both "child" projects.
-
Boards are just a way to view information in projects. You can have multiple boards to view the information in a project. The issues are in the project, not in the board. Making another board to view issues in a project has no impact on what is seen by the other boards. However, actions taken through one board on an issue…
-
But why do you need that? What problem are you trying to solve by have a project with child projects (given that is not even possible in JIRA)? Are you wanting to pull some sort of report that covers both projects?
-
As I said, there is no feature in JIRA that supports creating a hierarchy of projects. If you need to restrict access to the data per team, then you will need to have a project for each team. What is the purpose of the "head" project?
-
Hello @Christopher Leach Refer to this: https://community.atlassian.com/t5/Jira-Service-Desk-questions/Controlling-Customer-Access-Across-Multiple-Service-Desks/qaq-p/1025003 In a nutshell, if you want to enable external customers to sign up for accounts for any one of your service desk projects through the Customer Portal…
-
Hello @Hannah Welcome to the community. The permission referenced in that "Backlog - Versions" table is indicating that it is the Edit Issues permission that gives a user access to add or remove issues from a version. Generally, a user either has permission to edit everything or nothing when it comes to fields in the…
-
@Irene Jiménez Refer to this post and see if it answers your question. https://community.atlassian.com/t5/Jira-Service-Desk-questions/Controlling-Customer-Access-Across-Multiple-Service-Desks/qaq-p/1025003 If it does not please expand on your question to identify what point(s) are not addressed.
-
@Alexander Quintero Sorry, no, I'm not finding anything that would help with this in a quick search using google. You could search the App marketplace to see if there is an app that helps with this, or reach out to Atlassian JIRA support to ask if they have this as a feature request in their backlog.
-
When the Complete Sprint option is disabled that means there is an issue in that sprint that is part of a project where you do not have the Manage Sprints permission. JIRA does not prevent stories from other agile boards/projects from being added to a sprint. You may not see that extraneous issue in your sprint when…
-
There is no feature that supports a hierarchy on Projects in JIRA. What are you trying to accomplish with this? Why are you trying to create a project hierarchy? Do you need to allow each team to have access only to their own project? Can you have all the issues in one project and use a Component value to indicate which…
-
Do you use Organizations in your configuration of Service Desk? If you users are assigned to an Organization, and the Organizations field is set on the ticket, then the users would be able to see all tickets for their Organization through the Customer Portal. Perhaps that would give them the visibility that you want. They…
-
It would not be a full report, but you can create a JQL filter that uses the Request Channel as a criteria and that will tell you which option was used for ticket creation (portal or email).
-
Are you talking about customers or agents? And where specifically are these users "seeing" other projects?
-
Hello @Alexander Quintero Welcome to the community. Unfortunately that is not a feature that is available in JIRA at this time.
-
There is no option specifically to make sprints invisible. A scrum board will display the issues that are within the scope of the board's filter and will show all active and not started sprints that include one of those issues, or where the sprint was created in that scrum board.
-
When using Import to either create new issues or update existing issues there are some minimally required fields. Summary is one of those required fields. You will have to include Summary as an element in your CSV. Are you trying to add the value to issues that already exist in your project? If so, then be advised whatever…
-
Hi @Angie I mentioned that in my initial response. You need to look at the "Mark As Done" transition in the workflow to find the screen displayed for that transition. Then you would modify that screen to remove the field. You'll find the full list of screens under Settings (gear icon) > Issues > Screens
-
I was thinking of looking at a different view of the email log, as described in this article: https://confluence.atlassian.com/jirakb/troubleshoot-incoming-mail-in-jira-service-desk-790960076.html That view will usually provide a simple one line description of how the email was handled - either Success or Rejected with an…
-
Hello @Angie Did you also check the Validators for the workflow transition to see if that is requiring that data be entered in the field? You can find a list of the apps installed on your system from the Settings gear icon, selecting Apps from that list. Determining which app may be setting the field to required will…
-
Hello @Ruska Sisauri Yes, to use this workaround, the user must have Transition Issue permissions. Potentially you could add Conditions to each transition to limit who can see the transitions based on their Roles. You would have to give the "Transition Issue" permission to the JIRA Service Desk Viewer role first, and then…
-
What screen are you on where the "Next" button is disabled? Are you a JIRA Administrator importing the data through the System administration function for External System Import, or are you using the functionality available to an ordinary end user? Are you trying to populate values into issues that already exist? If so,…
-
Hello @Jürgen Scholtes Have you reviewed the log for the email handling to see if it provides any information?
-
Hello @Angie There are two things at work here: 1. Requiring the field to be filled in 2. Showing the field. You must deal with #1 first, and there are multiple ways that the field could be getting set to Required. a. It could be defined as a Validator for the "Mark As Done" transition in the workflow. b. In the Field…