Comments
-
Ok, got it - you're using a boolean field and a string as the input. Boolean fields can only have three values null/empty, true and false. Comparing them to strings like "yes" won't work.
-
Ok, that's good, because it means you have installed a valid version of the add-on (There's been a trend recently here on Answers for reports of add-ons not working, which, when investigated, it's because some idiot has installed a version that's invalid) On the down-side, that actually suggests that there's either a bug…
-
How did you install the add-on? Via the UPM (Admin -> Add-ons -> Find new add-ons) or manually via "uppload add-on"?
-
Ok, that's explained it all. You'll need to write a little bit of code to do this - you need a post-function that can read the current value and construct a new issue in the other project. I'd use the script-runner add-on as usual.
-
I'm confused by some of the question, and would like some explanation on other bits: >auto create issue Lots of ways, but the question here is when? When do you want to automatically create an issue - what is the trigger? >follow up ID I don't know what you want from "and follow up id" >based on custom field options What…
-
The relationship between projects and custom fields is very complex because it varies by issue type, not just project, and there's three ways to involve a custom field in a project. To extract "what field is where", you're going to have to replicate ALL of the logic that goes into it. So, I'm afraid the answer is "no".
-
I assume this is JIRA Cloud? This is something you should raise with Atlassian support at https://support.atlassian.com - the instinct for me is to read the log file and then report it to the add-on vendor, but you don't have access to Cloud logs, so a support call is needed.
-
But yes, you still have to remember to re-evaluate them.
-
Well, not really, because you've still got the original estimate. If you decide it's completely wrong, that's fine, you can change the remaining estimate and still retain the information that your original estimate was not as good as it cold have been.
-
Yes, it's a spectacular pain when software does that, you can't get any useful judgement on how well your estimates are working out.
-
I don't quite understand the question here. When you create a new workflow, Jira creates it with a single step, status open, and the "create" transition. That's a simple default. It would be silly to create a default step for "create" that is resolved or closed - the whole point of creating an issue is that you want it in…
-
It's because it's a LOT more simple to create a default step to pin the mandatory "create" transition on - if you're creating a new workflow without it, it's a right pain in the neck. Far nicer to have the minumum stuff there by default, even if you're going to hack it later. I've not actually tried deleting "open", but…
-
We're a community of end users. We don't have access to your system to configure it for you. I think you need to redirect this to your system administrators.
-
No, there's no such function. There is a simple version of the search which offers the more common boxes to select from (and a way to get at the other fields) and constructs a basic AND query, but no popup boxes. I think because you're already in a search, and it's quite useful to actually understand the query (by having…
-
I'm not sure what your question is about. Two things are not clear: * You seem to be reading a document that says something about JIRA making authentication requests, but what to? Could you tell us what document it is and what you're actually trying to do? * You mention wbosm-hp and Fisheye/Crucible. These are two totally…
-
Not really. Someone would have to generate a list of all the available versions of each end of the link and build it into a massive table of yes and no. It would be far more simple to select one version on one side because that's what you have installed, or would like to be using (e.g. JIRA 6.4) and then investigate the…
-
Remove the field from the "edit" screen and it will become read-only (leave it on the "view" screen of course). That blocks all edits though, so you might want to consider having it on transition screen and having transitions that then use conditions to only allow certain users to perform them.
-
No. JIRA doesn't have any form of field-level security in it. There are a couple of tricks you can play if you have Server versions of JIRA, including one add-on that is explicitly for it which works really well, but there's no options for it on Cloud.
-
Doesn't help with the main problem of the jump in numbers, but the last time I had to increase the number of users, the money spent on the existing users was included. To follow your example, I had 100 users and needed 500, but I only had to pay for 400, as I'd already got 100.
-
You could use any Unix variant to do this, not just Linux. Also, if you were on VMS, you could add a second directory to the apparent path.
-
Sorry, for the source, no, you'll need to read the history. Events are thrown at the end of the process, so only really have access to the current data.
-
Again - give us a chance, we do have other things in life, like family, work, food, cats and sleep.
-
The "issue moved" event contains a full set of issue data, as do all issue based events. I've not written vast numbers of listeners, but the simple and few ones I have written all start with public void onIssueEvent(IssueEvent issueEvent) { Long eventTypeId = issueEvent.getEventTypeId(); Issue issue =…
-
Give us a chance! It's only been 2 hours. We're scattered around the planet!
-
I already pointed at the documentation telling you how to run filters and view the results in the issue navigator. If you're not using OnDemand, you might want to refer to an older version - the "simple" search has changed formats between 5.1 and the latest release. The rest of it is valid for all recent versions of Jira.
-
I still don't know what you are looking for though. You're not defining a question, just what you need in the results. The issue navigator can list all of this and all you need to do is ask "show me a list of issues where ..." and the navigator will display it. The where clauses could include project, assignee etc, but…
-
I assume you mean Jira, as you've said projects? There's plenty of cross project stuff, but you haven't told us what reports you actually want. The best we can do without that is to tell you "define filters which return the issues you are interested in from all projects and work with those"
-
Well, the Jira issues macro only works for Jira. I seem to remember it's distributed as part of Confluence off-the-shelf already, but if that's wrong, it'll be in the marketplace. There's more at for using it: https://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro I don't know how Remedy might expose any of its…
-
Yes, I know, it's dreadful. So, you're looking for something like the "jira issues" macro in Confluence? That macro nips into Jira and displays the results of a filter - I'm guessing what you're looking for is similar - something that nips into Remedy and displays the results of a query of some sort? Or is it really an…
-
Depends on what you mean by "link". You can include simple urls in Confluence pages by simply typing them in. A lot of places use user macros to simplify this (e.g. [xyz-123@jira] here gives you a link to xyz-123 in our Jira). There are macros/add-ons for pulling in more detailed data, although I've not seen any for Remedy…