Comments
-
The main menu moved back to the top in Cloud a couple of years ago. So I'm curious as to what you mean with this question, as the menu bar already is horizontal.
-
No, they moved the bar back to the top a couple of years ago because the left-side one never worked properly (as everyone told them when they did it)
-
It's the same answer - you need to raise a support call with Atlassian and give them the error code.
-
Your second screenshot is of "Site administration", not "Confluence administration". An Atlassian Cloud site can be made up of Jira, Confluence, Bitbucket, Opsgenie, etc, and the administration of each application is different and local to each application. You need to go to Confluence and administer that, not the whole…
-
You must give them access to the space which contains the page. That's the whole point of the permissions - to allow people to see what they should and stop them seeing what they should not. View restrictions are cascaded, so the usual way to expose pages to different audiences is to allow everyone into the space and then…
-
What error messages are you getting when you try to save a page?
-
Scriptrunner allows you to run java or groovy (or a mix!), both of which are declaritive when it comes to variables - you can't just say "x = something", you need to tell the compiler that x is a variable before you can use it. So, on line 10, it's saying you have not defined a variable called response, and the object you…
-
Yes, that's correct. If you want to be able to order a list, you need it to be ordered by a value that gives each item a unique position in the list, which can then change when you re-order an item. You can't do that with priority (or, in fact, any other field in Jira). Imagine a simple case - you have three issues in a…
-
No, you're safe, the scheme is a purely event driven thing - it will only send email for new events.
-
That is an odd one, but it usually means actual "days in column", rather than "days in column in sprint". Imagine a workflow like to-do -> ready for dev -> in progress -> ready to test -> done, and you have 5 columns mapped with the same names If someone picks up an issue and shoves it into "ready for dev" without it being…
-
Welcome to the community. Short answer - page restrictions. If you use a restriction on a page, the padlock near the top right, you'll be able to say "only let these people/groups see or see and edit this page". The view restriction cascades - all pages under a page with a view restriction follow the view rule for that…
-
Jira only has business, Scrum and Kanban boards really, although they're quite malleable, they're not intended for this sort of stuff, they concentrate on getting stuff done and Agile methods. But, for arbitrary "boards" like that, I usually reach…
-
These codes do not mean much on their own, they are more markers to show the people who have access to the backend where errors happened. We don't have any access to Cloud back-ends, you'll neeed to report both of these codes to Atlassian directly, at https://support.atlassian.com/contact
-
Welcome to the community! There's no way to set the status on creation. The create "transition" lands at one point in the workflow. It's a bit like a starting a railway journey, once you've bought a ticket and got on the train, the track ends at one fixed place and you can't change where it goes. You'll need to do what you…
-
Not worth a photo - a carrot and a stick of celery used to pick up some blobs of hummus, lightly spiced with smoked paprika.
-
Most Atlassian server stuff implements most of the UI using "web fragments" which can be panels, menus, items or even css/js resources (and other stuff). Scriptrunner can make use of those and inject its own. In this case you'll…
-
No. Forget the dates and historical work, they do not matter. The process this stuff is designed to support is: * You have a backlog list of items * You should estimate them, at the very least the ones you are expecting or hoping to work on next * You rank them against each other, deciding broadly which ones should be…
-
My first instinct would be to add a post-function to the "rework" transition that would copy from the user-picker to the assignee. You'd need an app to provide the code to do that, there's no copy built in, but all the scripting and most of the toolbox/toolkit apps can do it.
-
One of my guesses was right then! Yes, I've got that issue on my watched (and voted) list, which is how I knew I could say "versions don't have components" straight away. My next step would have been "does the app have a REST API", but you've beaten me to it!
-
Oh, I just noticed something else. You've said "you" a couple of times - I just want to be clear that I'm not an Atlassian, I'm an Adaptavist (close partner of Atlassian, but not to the point where we get to design the products for them!)
-
Ahh, yes, that would explain how you got there. You're right, the free plan does not allow for permissions, they're fixed in place. But if you've gone up to paid, reconfigured, and then gone down, it does not change what you've got, just stops letting you change it! I don't think there's anything we could do, other than go…
-
Welcome to the Community! There is no "modify project of an issue", you have to move an issue from one project to another. The REST API does not yet have any support for moving issues.
-
I suspect the people who can not change the reporter are not in a group or project role that gets "edit reporter" permission. Check the permissions on the project to see who has and how to grant it to the users who need it.
-
What are the jdbc connectivity issues you are seeing in the logs?
-
There's two light misconceptions I'd like to clarify, probably coming from the way I've read the question. * Boards do not exist around each other - there's no "second board beneath a first", there are simply two boards. * Boards do not contain issues, they are a view of a selected set of issues. Most boards you'll see…
-
No, a Software project isn't really expected to be doing Customer Satisfaction, they're expected to be driven by the Product Owner working closely with the team, and being the person talking to the "customer". But there's good uses for it if you're not working as Software is built for, you'll just need to add something…
-
Jira can be hooked up to all sorts of communication systems. Email is built in, obviously, but there are integrations to Slack, Confluence, Mattermost, MS-Teams, Opsgenie, Statuspage, Trello, and, and, and... There's not a lot more we can tell you without a definition of your "team communication" - what are you looking for…
-
"Work on issues" in the middle of the list is the one. It says "Ability to log work done against and issue" under it.
-
The draggable line I described would support you. It's mostly cosmetic though - Jira already supports what you need by allowing you to put "in test" in the last column so your issues count as done when they reach in-test. I just think the many column solution is a cosmetically better view for some teams.
-
Personally, I don't think having a drag-left done column (a line you could drag left across the board to define the line between not-done and done) would be much of a problem, it would still support Scrum fine, especially if you had a "collapse" so people could make it look exactly like Scrum again if they wanted to. It…