Comments
-
Note the word "unique" in that last row's name. You have chosen to display a list of issues by Status and Component. Status is working fine, as you expect and is intuitive, but Component is not necessarily a single value field. So, an issue can have many components, and that's what this gadget is showing you. Taking the…
-
No, there's no issue in their view, it's working as intended. Has been that way since Jira 2.
-
You can make it work, but the instant you do it, you have rendered your Jira unsupported. As @Tinker Fadoua suggests, if you could tell us what the real goal is, we can probably give you some guidance on a better way. Without the context, my best guess is that you really should be writing an app to contain your page(s) and…
-
The project (or Jira or System) admins will have to remove you from the project role(s) that are granting you access.
-
You will need to talk to your database administrators. They have either hidden it from you or removed it. Jira doesn't have any code that might drop a database. You have to do that at the database level.
-
No. You only burn down points on completed stories. The "binary" approach your team is taken is not "drastic", it is what Scrum says. (Any other way, and you're lying to your product owners)
-
Your board filters should be based on what you want to see on each board. We can't define your filters for you here, as you have not told us what you want on the boards.
-
Use "move" from the tools menu in the issue view.
-
You can't create sub-tasks without the context of the parent it is going to be part of. So "create" can't do it. Go to the issue that you want to break down and use "create sub-task" from the tools menu
-
Copy them into the reports as needed.
-
Sub-tasks are part of the Core of Jira, not Software. You do not need boards to use sub-tasks. Just make sure there is a sub-task type in the project's issue-type scheme
-
For Boards there, you need Jira Software, not just Jira Core.
-
Could you explain what "Jet" is?
-
I do not understand what you are asking. Do you want us to correct your html, or tell you how to do something with a similar result in Confluence?
-
Atlassian have gone mostly for "standard" scrum - something that you told your product owner you were going to do is either done, or it is not. A half-done story is not done, so it goes into the next sprint by default. The "right answer" is, in Agile terms, to accept that while you might have got 99% of something done in…
-
It is not cleat what you mean by "Microsoft Login". Could you explain what your user directory is, and what Microsoft Identity and Authorisation systems you are using and how they are hooked up to Atlsasian Access?
-
It stops. And, as you suspect, generates errors. If it can't write to the database behind it, it simply fails every action that needs to write. Create, Edit and Transistion all fail. Moderately gracefully - they do not write any crud to the database, index or caches, but they can put some inscrutable text in front of your…
-
Jira Settings -> Issues -> Status is one way to get to the global list of status. Jira Settings -> Issues -> Workflows is probably more useful, as it lets you edit workflows with a bit more context (the status list above really is just the list of all available status, mostly out of any context where they might be being…
-
So, after some nagging from @Simon Haighton-Williams , I tried, and then got, an Oculus Quest. I'd shied away from it before because, although I could see the potential, I'd tried a Rift and a Vive, and lasted less than 2 minutes before I got queasy (arguably worse than the headaches that start the same time into a 3D…
-
>Ticket to ride, also fun, but ya know. The arithmetic to work out who has won. The one thing TtR fails totall. I tend to stick to playing it on a computer. One thing I'd love to see is an AI-backed camera for gaming. Stick it to the ceiling above your current game table, and let it watch the game. Feed it the scoring…
-
Start at https://confluence.atlassian.com/doc/upgrading-confluence-4578.html
-
This view is of the list of fields you have, it's not where you customise status. Status is a function of the workflow, you'll need to edit the workflow.
-
With the SDK, you don't need to have a server! Once the SDK is installed, you can run the following (I'm assuming Jira) atlas-create-jira-plugin (this will ask you for some basic information on your plugin) atlas-run The second command will compile the skeleton plugin, download the named version of Jira (see the created…
-
Ok, I would break this task into two parts. First, get a proxy working with http, then, second, add httpS to the proxy. So, first, see https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html There's a lot there, but if you follow each step, it will…
-
No, you're not an idiot. Atlassian have documented all of this, but there is... just... so... much... Lots of options, lots of divergence, it's confusing for even those of us steeped in it. Don't worry about the tagging either. One of the big complaints the community answerers have had is not having any clue whether people…
-
Switching to Gsuite or SAML would solve it because the accounts would belong to your organisation, not the individual. You would have a migration exercise to do of course, off Atlassian accounts.
-
Jira Core boards do not have a "create" option. You get one board for each project automatically, if you are on Cloud as you tagged this question. But as you said Jira 8, that says you're on Server, not Cloud. Server Core projects do not have boards (but can be included in Jira Software boards if you have Software)
-
Glad to help! We all forget bits of Jira at times, irrespective of experience!
-
No, that's not possible, even with SR. A transition has a single end-point, it is always going to land in one place. You have a couple of options. * With conditions:* Create transition from status 1 to status 2, with a condition that says "only if button = yes" * Create transition from status 2 to status 3, with a…
-
If you log in as an admin, go find the "field configuration" for this project and issue type (easiest to go via the project header and settings), then you should be able to change the "renderer" for the Acceptance Criteria from "plain" to "rich" or "wiki" (not sure which you might have)