Comments
-
This is one of the reasons the fields are locked. You should not apply those fields to anything other than the Epic issue type. JIRA Software expects only that issue type to be set up as an Epic, and things *will* break in interesting ways if you achieve any of what you've just said. Do NOT hack the database either -…
-
>It can be % of time taken, scope done, money invoiced or resurses used That is exactly my point. I think you've misunderstood what the others are saying, and have understood what I've been saying. The percentage is utterly usless unless you know what it is measuring. A percentage without knowing what it is a proportion of…
-
So, let me repeat this back to you to ensure I have it clear: These two calls work, pulling back issues: * curl -D- -u xxx:yyy -X GET -H "Content-Type: application/json" /rest/api/2/search\?jql\=createdDate%20%3E%3D%20-30d * curl -D- -u xxx:yyy -X GET -H "Content-Type: application/json"…
-
Right, I meant specifically the url based query with just the project - does that pull back all the project issues for GS?
-
That's a question that runs to answers involving entire libraries worth of documentation. Get yourself on some Linux courses first, and then have a look at the Atlassian training options. It's not a subject someone can just start on, you need to absorb the knowledge of the OS, and the applications, and the best place to…
-
The "estimated fix date" is a custom field (possibly added by an add-on), that belongs to your system. You'll need to ask your project owners or admins what the field is intended for.
-
The docs will tell you to use the latest version of JIRA and then go to the Cloud. Recently however, this has been breaking, and I'd try 7.3.latest at this point. 6.4 to 7.3 should be possible in a single step, and I'd ignore the Cloud part of it until you've got that upgraded.
-
Ok, so you say you got one mail, and I assume other emails are arriving? Can you check the email error queue to see if the subscription mail is in there? Could you increase the frequency of the subscription, so that you get the mails quite a lot - do any of them arrive at all? Also, on the subscription, make sure you have…
-
Currently, there is no way to do this - you can either search users globally, or not.
-
I don't know what those icons are, but they're not core to JIRA off-the-shelf, so they're being provided by some add-on you've got. Without knowing what add-ons they are, I can't tell you a lot more.
-
Hmm. What happens if you search just for the project and drop the date part? i.e. just "project = GS" or jql\=project%3DGS in the url.
-
Mandatory fields are not related to screens. A screen is just a list of the fields, it says nothing about their behaviour. There are broadly two ways to do mandatory fields: 1. On the transition - a validator is running. You'll need to have two separate workflows, one using screen A, and the other for B 2. Field…
-
I'm sorry, I missed the email updates. I can't really help you with the code without writing it myself, and I don't have the time to do that (and I'm not a coder, so if I did, it probably would not be that good anyway) You'll need to start with a proper specification too - "extract aging report" doesn't tell us enough.…
-
Possibly. You need to add a new function to JIRA. The normal, recommended way to do this is to use an add-on. Three options are to * write it yourself * find an add-on that does what you need and add that * find an add-on that allows you to write code directly inside JIRA and write the code in that. The third option is a…
-
The link display function does not support searching, so you'd need to find or write an add-on that could provide the searcher for it, as well as something to hook into the function (it's not a field really, it's an informational display) If you've got an add-on that provides scripted fields, you could take the links from…
-
That seems a little over the top. As you say, Bitbucket Cloud is free (for up to 5 users) and the setup on Cloud is "sign up", there's nothing more to set up. Although you do have to give it a few minutes for the server to become active. Once it's running, creating an empty repository takes a handful of clicks. Ignoring…
-
Ok, you'll need to read the log to see what errors are being thrown when you try to do the column to column drag and drop.
-
Most of the add-ons in the marketplace can be single direction, or bi-directional.
-
You've probably not re-installed, configured or upgraded the add-ons providing those missing functions, or they have changed their locations during the upgrade.
-
The usual thing to do is have a workflow for the main issue that includes a condition "can not close this issue when it has open sub-tasks". That condition is a standard one available in JIRA off-the-shelf. A second option is in JIRA Software - a main issue can be moved to done when its last sub-task is closed. With a…
-
Does the filter show you the issues you expect to see when you run it in the issue navigator?
-
You could ask the user to visit the issue and look, but I'd suspect there's a couple of other problems. First, why do you need to explain the workflow? That tends to mean it may well be quite complex and hence not that good a process. Second, if you draw in a workflow diagram and explain it, that's fine, but when it…
-
There's no mechanics for doing anything like that. The code has a show/hide function for "condition tells me pass or fail", but nothing else. The conditions have no access to do anything other than return true/false.
-
Ok, what are the board columns? One for each of the three status above?
-
It's issue.getParentObject().getOriginalEstimate() See this and the rest at https://docs.atlassian.com/jira/7.2.2/com/atlassian/jira/issue/Issue.html
-
That still suggests the workflow does not have a transition (or does have one, with a condition you're not meeting) for <something> -> <status in the done column>
-
There's no native function to do that in Confluence. I think you'd have to write a user macro of some sort to pull out the diagram from JIRA into a frame or something.
-
Ok, so not the ... menu, but the workflow one. You'll need to check exactly what is happening here. Ignore the workflow status for now, and look at the transition name on the workflow menu. Then go to the workflow editor to see where it takes you, and check where it lands and then what column that status is in.
-
The ... menu on issue view does not contain transitions, so I'm not sure what you're clicking.
-
No, a condition simply returns "true" or "false" to represent "this transition can be used at this time" However, for what you're trying to do, just rename the transition in the workflow editor.