Comments
-
Rob, If you click remove you can see what group has been granted access, my guess is public. The public group can be applied to any of the permissions on the scheme. Please click remove to see what it is and if it is public simply remove it.
-
Tim, This is not possible through delivered JQL - https://jira.atlassian.com/browse/JRACLOUD-41039 I know people have used scritprunner to get information out but I am nor sure there solution would work on cloud. Another work around that you might try is require to search issues moved from one project to another. Create a…
-
Yes the quotes does prevent issuetype, etc. but it seems to have always allowed a project key that matches to be pulled out. We had a project key of work and test that when running quotes around it always got pulled out. So if it is a bug it has not been reported and it has been in there for multiple versions.
-
I believe this documentation should point you in the right direction. https://support.atlassian.com/jira-software-cloud/docs/configure-estimation-and-tracking/
-
Matthew this is a limitation in cloud and I believe that you found the only app that even comes close to providing the functionality that you need. I believe that it will work for you you would just do something like this 1. H1 Tag 1.1 H2 Tag 1.2 H2 Tag 1.2.1 H3 Tag 1.2.2 H3 Tag
-
Michelle, That is smart query and has been around for a long time. My guess is that this is the first time you have noticed it trying to help you out. Usually when it runs you will see the following pop-up: You can learn more about smart query here:…
-
@Allison Beaudry I am sorry I should have noticed that you were using a next-gen project. Is all you should have to do is change it from current issue to trigger issue and then you should see your field that you originally created and not the custom field that you had.
-
Sorry I just looked at the screenshot above and you are using a next-gen project. Let me take a min and get the steps put together for you.
-
You need to make sure that you have added the field to the create screen for the issue type associated with the request type. Once you have done this you can add it to the request form. You can check the screens by going to project settings -> screens
-
Rob, You have a group, most likely public, that you have granted access on the default software scheme. You can click remove to see what group it is that you have granted access and remove it or get a better understanding of why it was granted. Someone applied it to administer project which I think is a mistake and should…
-
According to their status page there were issues yesterday but none reported today. You might look at rasing a request with their support if you are experiencing issues. https://status.zephyr4jiracloud.com/ Support - https://support.smartbear.com/open-ticket/
-
When creating a Jira site, automatically an organization is created. This organization can't be deleted. There is a feature request suggesting the implementation of this ability: * Allow organization administrators to delete organizations There is a workaround that used to work that you can try. You can delete these…
-
Chino, I have seen this before and there are several things that can cause it. You will need to check your logs to determine the issue. You can use this KB to troubleshoot the issue - https://confluence.atlassian.com/jirakb/create-project-fails-with-unknown-error-in-jira-server-818580338.html
-
Here are the steps I took to get it to work. I added a custom field it has to be User Picker (single user) - https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/ I then associated that custom field with the proper screen(s) on the project…
-
Once you select copy from it should look like this You will then need to click copy assignee from current issue to get additional options. If you have your custom field configured correctly it will show up as an option to copy from.
-
choose assignee and then select the three dots on the right and choose copy from. This will get you the option to copy from another field.
-
It should but it all depends on how you have the automation configured. I looked back through the screenshots and never saw a automation that was correctly configured. You need to make sure the field you are editing is the assignee field. You then copy from your Select Program manager on the current issue. I added a…
-
You issue was not assigned so no email would have been sent. You need to look and see why the assignment is not occurring.
-
Just remove the reporter is customer feature and I believe you will be good to go. You might want to limit it to certain request types that this will be happening on if it does not apply to all requests.
-
Were you able to get this to work?
-
This week for the same challenge is all you need to do is post a comment. Looks like they are changing things up.
-
Allison, I built out everything out and it seems that you have it configured correctly. The issue I ran into and I believe that you are having is the condition reporter is a customer. If I used a test customer account to send in the request it works perfectly. If I tested raising a request on behalf of someone else then it…
-
I believe that you can get the badge multiple times. So you may have received it but it is no longer visible in your trophy case.
-
How come I feel like this will become a like fest :)
-
I have the same question. I think it might have to be 5 like by people in the kudos pilot. I am going to test this out by giving you a like now and hopefully 4 others will as well.
-
No unfortunately not.
-
This is not delivered functionality. There are some apps in the marketplace that allow for delegated group management but not user management.
-
Do you have any apps installed like BigGantt?
-
I forgot to say that this really will not work with a pie chart but you could create a report in the service desk that would be a line graph that could display this information.
-
You can create a filter that looks at the SLA using JQL. For instance if I wanted to see all the breached first responses I would do "Time to first response" = breached() You just have to know the name of the SLA and you should be able to create the filter.