Comments
-
No, JQL is not SQL, it is just for finding issues, and has nothing to say about output, formatting, or even any data it might be pulling back. The result literally is a list of issues. If your users are confused by the names you're chosing for field values, it would be better to use more clear names!
-
The relationship between a board and an issue is defined by 1. The JQL used on the board 2. The coded settings for the board Your database query is, quite simply put, going to be horrid to construct and valid only once. You'll have to replicate the JQL in SQL (they are very different things) and then apply board settings…
-
That's pretty much what the announcement banner is intended for - a short warning that things are changing, whcih I usually add either the JIRA issue ID to, or point people to a confluence page for more information if it's a bit longer than a simple jira config change.
-
The config screen you have in your last screenshot explains what is ahppening. You have a column called "to do" which has the status "to do" in it. The second column has two status in it. When you try to drag a card into that column, you are asked which status you want to use, but it's not displayed because the point of a…
-
Yes, I think it's purely broken gadgets. But the errors you're getting are implying your gadgets are looking in the wrong place, like the base-url is incorrect.
-
You cannot close your sprints because you have not finished the issues in it.The far-right hand column on your board must contain all end-states for issues. You need the status Done and Complete inthe "complete" column on the board. If you insist on having duplicate meaning status of done and complete for the main issues,…
-
Not specifically for JIRA - I've used Google Analytics on it, although we found that there was so much "view" activity, it wasn't telling us much of any use. Bit more useful on Confluence. I don't know how GTM might be used.
-
"Pending Reason" is not a standard JIRA system field, so I'm afraid we simply can't tell you. It's a custom field in your system, either one your admins have added directly, or indirectly (by installing an add-on that adds one automatically) If you can't fill the field in on issues, then it is not on the create or edit…
-
It offers you a selection as you type, so I never bother being fussy about case.
-
Try using the clause statusCategory = in progress It's an advanced JQL function
-
JIRA doesn't internally track read activity, so you'll need to add stuff to do it for you.
-
1. Not yet. There's a couple of requests to do it, but at the moment, a Service Desk project can only have one knowledge base. Although you can have >1 project linked to a knowledge base. 2. It's not a bad thought, but if you are worried about your users having different portals, the right thing to do is a single one, with…
-
The far-right hand column on your board must contain all end-states for issues. You need to move the status "done" into the "complete" column, so that the sub-task can be in the right column when it's done. "done" and "complete" mean roughly the same thing, so your main issue workflow is pretty unclear. In order to stop…
-
That looks like an error in JIRA, rather than your script. It suggests your admin access to the console script has timed out or ended before the script is finishing.
-
You need to ensure a valid version of the add-on is installed and active. The error you are getting is a simple "cannot find something the add-on provides" error.
-
Ok, if the base url is correct, then the next step is to look at the add-ons - I'd try to disable and then re-enable them. If it still persists, the next step is to look at the logs in detail.
-
Admin rights mean admin rights, it's not an automatic "can see everything". You don't have to put admins into the space permissions at all, and if you don't give them "can use space" or you exclude them from restrictions, then yes, they will not be able to see the contents. An admin can always get to the permissions for a…
-
Correct, the business boards are very simplistic, and can't handle multiple workflows. The Scrum and Kanban boards in JIRA Software do handle multiple workflows and let you combine status as well. You don't have to be working with software support or development to get the benefits of boards out of them at all.
-
Yes, it's tracking the time you estimate and take to do the work. >a day of effort per developer per day is required meaning overall the user story would take only one day to complete No, it takes three days of effort to complete. The time IS accurate and it's useful because you can say "we have X days work to do". You can…
-
No, that's my point - you are wrongly assuming that the time shown is elapsed time. It is not. It is tracking working time. Your three developers are each saying "1 day", so there are three days of work to do. It's irrelevant how many developers you have on it, it's three days of work.
-
Has the base url changed? Can you check and correct it if it's not a restoration over the system the backup was of?
-
You are confusing elapsed time with working time. Your three users are each estimating it's going to take a day's work for each piece. So the actual time taken IS three days. It might well be delivered in one day, but it's still taking three days to do all the work. It's not actually much use trying to track elapsed time.…
-
Your user *must* be matching one of the rules that allows browse rights. I'd re-check all the role memberships of course, but I suspect that they either have "create issue" rights, which would allow them to become a reporter, or they are selectable from the custom field you have in the scheme which would also give them the…
-
The workflows created and applied to a project when it is created are set by the "project type" you choose when creating a project. You have two options: 1. Create an add-on that adds a new "project type" with your workflows 2. Use the option at the bottom of the selection box for "shared configuration". The downside of…
-
It looks like you might have mapped your customer status directly on to your JIRA workflow. One of the reasons people use Service Desk is that it can hide the internal JIRA status from the customer by grouping them together into more simple ones. See…
-
Most of the built-in macros are bundled into "system" add-ons. You'd need to get the source code of those, make your changes and recompile them, then deploy them to your server, replacing the system add-on.
-
You don't say whether you are using Cloud or Server. If you are on Cloud, then Atlassian limits your customisations to things that they can support, as your system is running on their kit and you're relying on them to support it. If you are on Server, then you are free to customise it completely. Atlassian may not support…
-
The development instances are time-bombed at 3-4 days depending on version. As Pedro says, just stop it and start it again. Remember also that a dev install is not a "proper" JIRA server - it's modified to help support your development work. It's not really suitable for doing support or end-user testing work.
-
That requires coding, and I suspect it's coding in the system add-ons that make up the off-the-shelf JIRA, not something you can do with a simple add-on.
-
Hmm, ok, that suggests that the customer is not a customer in the target Service Desk. Can they raise new requests in the Service Desk you've moved to?