Comments
-
See the accepted answers.
-
No. You are wrong. As a user here in community, you are using your Atlassian account. Now imagine that you are using a Cloud Jira for your work as well. You're saying that you would be happy for me, as an admin here but without any access to your Jira, to change your name on your Jira to "Gabriel Does Not Understand This…
-
You don't have board administration rights.
-
Check over the "issue type screen scheme" for the project. It will tell you what "screen scheme" is in use for each issue type, and then descend into that to see exactly which screen is in use for "create" for the issue type you are lookig at.
-
You will need to improve your connectivity to fix that at the moment. There is another option being developed, where a Data Centre install will be able to have nodes geographically distant from each other, but it's not there yet. (You could actually do that now, having nodes in two remote places, but it's not supported and…
-
These are some excellent illustrations of just how weird a human's perception systems can be. I'm quite fond of the the maid/crone one, because it has a very unusual effect on some people - we see both at the same time. I think it's weird because the more geometrical ones like the Necker cube don't do it. I see the cube…
-
Please, stop SHOUTING You can't revert back to the old style layout on Cloud, Cloud users are stuck with the left-hand side bar now. If it is important to you, then you should migrate from Cloud to Server - the new layout does not look likely to go to Server for a long time. (For which I am glad, because I think I like the…
-
I don't think you've understood what I've said. Please explain how to code for all the various estimating on sub-task strategies that the Jira user base might use, and how partially done estimates work with the flat "done or not". Once you can do that, someone can write it. VSTS adopts one strategy and fails scrum…
-
@Veera Marni- we're a community of end users, we're not going to spend ages trying to replicate your system just because you have an issue with it that you are not prepared to look into for yourself. Even if we were support, the correct response was "you need to do the debugging on your system, or if you really can't,…
-
To be fair, there's no other way to add more information, unless it's an edit to the main question, which tends to make it more and more unreadable. This is a reason I was disappointed with the move from Confluence questions (where you could comment or answer) to the more primitive Lithium platform.
-
If you want a fix, you'll need to come up with a strategy that meets all the different ways of adding up the hours without breaking the basic "deliver or do not, there is no 'try'" principle of Scrum.
-
That won't solve anything. It will provide a cascading select that offers Service or Data (and then the same sub-lists) on all issue types. Jobin's solutions are still the only useful ones.
-
It's clear - your account has no access to whatever Jira Service Desk portal you have landed on. Contact the owners/administrators of the system you're trying to use. If you don't know who they are, then get in touch with whomever sent you to try that portal.
-
Ok, when you run in the console, there's no context - it's something you're just running in Jira. When you run in a post-function or validator etc, you have the context of it running as things happen in the issue, so you have an issue object available to work with. For console testing, I'd pick an issue and (temporarily)…
-
I'm not aware of any alternatives. There are some add-ons that have built-in access control, which can effectively say "only these 10 people can use this", but you still need to licence them at 100 users because that's the number of Jira users you have.
-
I should add that I learned this "humans are bad at logic" first hand, when stuffing up the first big development project I was supposed to be the main coder on. 20 years later, I still have to step back and think "remember, you're not Viz's Mr Logic, your instincts here could be wrong". For me, it's especially on searches…
-
If you don't understand, then you should never have done this. There's no point me explaining the other things you have damaged or may have damaged, the fact is you've done the wrong thing. I've already given away one of the other two main areas you've messed up, and I don't want to give anyone else any idea that this…
-
Yes, but not directly. You'll need to export the data into something Jira can import. Probably CSV.
-
Ok. So you have missed a whole batch of stuff, and you have corrupted your Jira. That's all I needed to know. My advice stands - DO NOT DO THIS.
-
Yes, admins can edit the system dashboard. But your (reasonable) assumption that it will be accessed the same way as user dashboards is wrong. It's an admin function, so it's buried in the admin menus, not a click on the dashboard! Go to Admin and search for "dashboard" (I can't remember which section it's in)
-
Humans are often bad at logic, with their instincts leading them astray, especially when there are negatives in something. "Is this a tiger?" is an easier question to us than "is this not a small cat?" - the "not" causes us to have to do a lot more work to get the right answer. I found the trick is to look at each clause…
-
Your best bet is to comment and vote on the bug over at the link you've given. Commenting here in the community has no weight at all.
-
I dug out this on creating the boards - https://www.atlassian.com/agile/tutorials/creating-your-agile-board but the column configuration is no more complex than I said above - just put different status in the to-do/done columns
-
When a trial ends, the server keeps running, it just goes read only. You should still be able to log into it as an admin and use the admin sections, including the place to add your new licence.
-
For what it's worth, status != Done OR status != Closed does not work because it's logically wrong. If an issue is Done, it can't be Closed, so clause 2 returns true, and if it's Closed, it can't be done, so clause 1 returns true. As one clause is always true and you've used OR, you are always going to get a true result.…
-
This will not work. You can't change the status from edit. You need to transition the issue, during which you can ask for edits, but Status is not a field you can change.
-
The boards have changed significantly in the last 5 years, but we can still try. What exactly does the board filter say, and are your "closed" issues showing as being in the current sprint?
-
There are a LOT of people who really don't want the Cloud navigation to go anywhere near server. I'm not so strongly opinionated, although I would say the Cloud navigation is nowhere near ready to go out to users yet.
-
The whole point of unmapped status is that they do not appear in any column. If you want a status to appear on a board, map them to a column.
-
Well, in the new beta issue view, the transitions are shown as a status drop down which lists all the target status for possible transitions. (I don't like it a lot, it breaks the "two routes to one status" trick a lot of people need to play)