Comments
-
Yeah, that's something I see as wrong in Agile, as humans instinctively see green as nothing to worry about, and blue as something they might.
-
A cascading select is a Jira off-the-shelf function, so yes, I would strongly suggest a broken add-on. However, you appear to have configured an app that expects a number field to look at a cascading select. I would start by not doing that. I'm not familiar with "mesilat" by memory, but try typing it into the marketplace…
-
Transition is not a field, it is an action, you need to give it a transition id to perform, with fields to be updated inside that. Please have a look at…
-
I thought that might be it, although the behaviour you're seeing is not quite the same as it was (leading me down the "no components" path) You do not have the Components field on the edit screen, so you cannot edit it. You will need to add it to the edit screen. If you're unsure how to do that, click on edit again, then…
-
Atlassian don't do admin on other people's systems, you are expected to be able to do it from their standard "Jira administrator" docs. If you need formal help, you'll need to engage one of their partners if you need help (they offer a wide range of assistance, from light-touch admin, general advice all the way through to…
-
Without giving us the errors, we can't really tell you a lot beyond "you are probably giving it the wrong settings"
-
Because it does not work. Rank used to be numeric, but they changed it because it fails in all but the smallest of systems. To use your example, of inserting a new item at 34 between the existing 34 and 35, you would need to push 35, 36, 37... down one point in the list. Now imagine your list is 4,000,000 issues long.
-
There is no way to "disable" a field. However, could you also try the "edit" screen - how does components behave in there?
-
It looks to me like you have an app installed called "go edit", and the licence for it has expired or been removed. You'll need to remove the app completely, or get a new licence for it, then re-index.
-
No, it will not work, because your "business unit" field has nothing to do with people or their accounts. It's just a list that has no link to people. You will need to set up groups of people to represent the business units (or roles, but you'll find groups more intuitive)
-
You would need to hack some of the core code in Software - a sprint really should be showing your estimates, not remaining.
-
You'll still see that on "proper" unresolved issues even if there is one. I just want to completely rule it out!
-
Define "pull"? Custom fields are fully reportable, you don't need to "allow" anything. I think you need to define what you think you are missing?
-
You have an app added to your Jira that is pointed at a field it cannot read. The app is expecting a number field, and you have pointed it to what I would guess is a a cascading select. Note the "mesilat" a few lines into the error message - that is a class name for an app.
-
What happens when you click on the "none" next to components? If it's absolutely nothing, then the project has no components defined.
-
You will need to move the child page to somewhere less restrictive, or relax the restriction on the parent.
-
I assume you mean the community here? Sometimes, you'll find a thread is locked (usually because it's attracting spam or sock-puppets). But it might also be the type of post - discussions don't have answers or fully threaded comments. If it's not community, could you explain where you're struggling?
-
This has nothing to do with sub task numbering - could you ask a new question? (Although as a pre-answer, sub-tasks are not counted as backlog items already, so please make sure you explain how you have included them, and why you don't just turn that function off!)
-
You need to make sure you are a project admin, then go to the settings for the project. Find the components, and add at least one. The component/s field is greyed out because the project does not have any components to select from yet.
-
"Bricks" is unclear, but there are two things you're looking at: In Jira, status all belong to a category. The three categories are to-do, in progress and done. The colours of those have been changed lately to improve contrast and avoid colour-blindness problems (earlier versions were blue, yellow, green). They are fixed…
-
Jira Core was 2016 from memory, try downloading Jira and look for the "old versions" to see the release dates. The "cloud release" of service desk was at the same time, when Service Desk moved to be an application - 7.0 Server, Cloud major release a few weeks before, before that, Service Desk and Software were "add ons"…
-
I am sorry, I just do not understand what you are asking for there. An example of what you asked for in the question is simple - create an issue in Jira, open up the view and select "create sub-task" from the options menu. Complete that, and you now have an example of Task and Sub-task.
-
It's not a simple "number of votes" - that is one factor, but there's also the support requests from customers that it might affect, the overall plan for developing the software, the new features that could be added, priority against other things, data coming from TAMs and integrators, and, and, and.
-
It looks like something (the browser?) doesn't support displaying them. The easiest fix is to not use them at present.
-
The new colours look right to me. Better than the old blue/yellow/green Green universally means "good", which translates to "nothing to do here" in Jira, so it's still the best choice for "done" Blue is a relatively neutral colour, and grey is completely neutral, but they do have a good contrast. Red and Yellow are bad…
-
You can have many different issue types at both task and sub-task level, you are not limited to those two names. Sorry, parameterise what? Example of what?
-
Strictly, one, as you are supposed to use one account per person. Technically, Jira doesn't care how many times a person logs in.
-
No, Confluence expects you to "obfuscate" by "not putting stuff you don't want on the page on it"
-
An API and a SDK are totally different things. A SDK is for developing code. An API is for creating interfaces with something. You will want to write your code in the SDK, and then refer to the (REST) API when your code needs to talk to Jira.
-
This is a long-shot, but could you log in as an admin, go to Admin -> Issues -> Resolutions and look at the list that is set up? Is "Unresolved" listed there?