Comments
-
Your administrator needs to read the logs to find out why it is stopping.
-
Deletion is not part of workflow. It's a separate action, one that should be used VERY rarely as it completely destroys ALL the issue information. If it's part of your standard process, then your process is wrong. To automate stuff as you delete, then you need to find or write a listener that can catch the "issue deleted"…
-
Ok, great. There's a bit of doubt as I'd expect something slightly different, but it's not worth chasing yet. On the left-hand menu, can you click on the second line, for "Application Access". At the bottom right of the screen that displays, there should be a mention of Jira Service Desk, including an install mention. Is…
-
This forum platform is still lacking many of the functions Confluence Questions has, and moving/removing stuff is one of the these. The way you are using your system now means that what you're doing is a perfectly good approach, and it will work fine for you. My discussion was not to try to tell you to change (I'd rarely…
-
Log in as an admin, use the admin cog to get into the menus, and then use the search to look for "application" (it should auto-fill some options for you) Depending on version, it could be about managing applications, application licences or usage. But it will be obvious on the list you get
-
Ok, so I think we should try something more extreme. The cwd_directory table should have an "enabled" flag. Stop Jira, use SQL to flip the flag on the external directory so it becomes inactive and restart.
-
It really is simple - Atlassian have stated the new UI is not optional on Cloud and there's no way back. So your only option is to go to server. Atlassian do read these posts, and they have recently committed to reading them a lot more. But on this topic of the new UI, they've said what's happening.
-
A board can include issues from many projects. You need to stop thinking of a board as being "in a project", as that's not true. It can look like it, and the UI misleads us into thinking it in places, but a board can pull in many projects, and a project can be included in many boards. >And if all are of the same type you…
-
Remove the post functions, automation or listener that is doing it.
-
Yes, it is.
-
See https://confluence.atlassian.com/jirakb/cannot-reindex-jira-due-to-expected-exactly-2-rows-the-maximum-marker-row-and-the-lowest-ranked-row-for-rank-field-779158916.html
-
Could be either from that spec. Have a look at https://www.atlassian.com/blog/jira-software/server-vs-data-center-whats-right and https://confluence.atlassian.com/enterprise/jira-server-and-data-center-feature-comparison-953651628.html
-
I can tell you have not bothered to read the rest of the thread where the reasons for that comment will become clear.
-
Nope. That tells you about the board, not the project. Boards do not belong to projects, and you can point many points to a project. If I create a Scrum project, I get a scrum board at the same time, but I can point a Kanban board at it if I want as well.
-
You've got something in your workflow that is trying to check the values of a custom field with something, but that custom field has been deleted from Jira. You'll need to check your workflow post-functions, conditions and validators.
-
Jira Core, Jira Service Desk and Jira Software are three "applications". Jira Service Desk and Jira Software both run on top of Jira Core. Effectively, Jira Core is a "platform" for them. It provides issues, workflows, users, fields, the main interface and so-on. Service Desk provides a layer including portals, SLAs,…
-
The QA team probably needs to be prepared to accept an uneven flow of work coming from the development team until the dev team has got its velocity tracking and estimation right, at which time they'll be able to to be mostly sure the deliverables arrive at by the end of each sprint.
-
Look for the actions menu on the issue, there should be "log work" in it. If it's not there, then go to the project admin area and look at the permission scheme.
-
You (and a lot of us) wanting them to revert is not the same as them needing to do it. I'm afraid the old UI is not coming back unless enough of us vote with our feet and move to Server/DC
-
Move to server if you want the older UI back.
-
This sounds like a problem with your development team, not an issue with Jira. I think you need to talk to your development leads, not the Atlassian community?
-
Have a proper read of the discussion above - there's two topics really. 1. "to give a user access, grant it to them" and "if you don't want them to have access, don't give it to them" - this is not complex at all. 2. The default permissions are wide open and have to be unpicked if you want to lock anything down. This is…
-
There's two problems here: * Label fields do not take "options", they take "label" objects. * Label fields do not have a list of options, you have to add new labels to issues. See https://docs.atlassian.com/software/jira/docs/api/7.12.1/index.html?com/atlassian/jira/issue/label/LabelManager.html probably
-
I'd take a look at Comala workflows - https://marketplace.atlassian.com/apps/142/comala-workflows?hosting=server&tab=overview - your question is pretty much their main user story!
-
With the menu on the left, it tells us you are on Atlassian's Cloud Jira, not server, where the layout is very different (and poor, in my opinion) When you're looking at the Atlassian docs, make sure you refer to the "Cloud" versions of them, where you'll get more appropriate explanation of the layouts and options.
-
This has nothing to do with this 5 year old question. I'd suggest you ask a new one to get some visibility across the community. However, at a glance, as you're running the code in a transition, getKey is going to return the key of the current issue, not the one you are trying to create (and you can't know the key of that…
-
Yes, the client can do offline reporting, but bear in mind the reports will be obsolete as soon as they are disconnected. Yes, you need to pay for the licences you use.
-
I'm guessing you are on Server, where it's not available yet.
-
No way to know without page load analysis. I've found miniOrange to be slow in the past, as it seemed to want to re-authenticate on every page despite having logged in, but that was one client, years ago. Try creating a local user in the internal directory and logging in as them. If they get a fast page, you know it's your…
-
Indeed, Jira doesn't do it off-the-shelf because it is totally the wrong thing to do. "Story points by person" only makes sense when you have teams consisting of 1 person. Plus, it's illegal to do this sort of reporting in some places, primarily Atlassian's second biggest marketplace.