Comments
-
There's no add-on I can find for any links with AppVeyor. You will need to * Define what you actually want from an "integration" * Consider where to write it ( add-on for JIRA, code in AppVeyor, code outside both as a bridge, or a mix of those three) * Head over to https://developer.atlassian.com/index.html if it's a JIRA…
-
You don't - that's just the way it's coded. I suspect you could add a spot of javascript to the banner to get it to default to something else, and you could always have a look at the core code and modify that.
-
Yes, it used to be a little neglected, but Monika's team has grown significantly since I started, and got on top of all the addons that were falling behind now, so you can expect it to be updated more frequently in the future. We've also got a policy of not just saying "data center compatible" until we've tested it and…
-
There is the basic "like" feature built in, but I suspect what you really want is a "rate macro". The only one I'm familiar with is the Adaptavist one ( https://marketplace.atlassian.com/plugins/com.adaptavist.confluence.rate ) but there are others in the marketplace that you might want to try I should say that I work for…
-
Ok, so when does that happen? As soon as you change the sprint? Or all the time?
-
Might be worth explaining what you think is wrong with it - what is this "unreliability"?
-
Depending on how often the data is going to change and who should do it, I tend to use: * include (includes a whole page, although there's nothing to stop you having a page that just says "1.2.3") * excerpt (handy if you have a "project release" page and you want to update the version in the main page, and have it cascade…
-
An improvement here would need JIRA to support the firing of events for changes on links. I'm not sure ScriptRunner could be made to handle anything without support from JIRA.
-
This is not technically correct in the background, but an easy way to think about scripted fields is that "they store their data in the index, so they only get updated when an issue is indexed". The changes you are making to issues at the other end of the links do not trigger any indexing on the Story. Sadly, for links,…
-
It's actually quite hard in JIRA, and you need to be clear on how you're measuring things. Generally, people will take one of two approaches to measuring the time. Both are valid and both are useful, because they measure different things. One is elapsed time, which, in JIRA, is almost always the time between entering one…
-
I'm not sure I'd bother doing this in Jira. Sounds convoluted and complex with no real benefits. I'd just stick "p4 sync -c <myclient>" into cron on the Jira machine.
-
That potentially contradicts itself. Forget about "your network". Is your Confluence available on the internet? If you gave me a login *for your confluence* (not your network, *just* confluence), could I log in from my house?
-
>Our Confluence is available on the internet, but it is for internal access onlyEither it is available, or it is not. Which is it?
-
Same way you get any access - expose the service to the internet. Is your Confluence available on the internet yet?
-
I'm not sure why you'd bother with Postfix -> local file. Why not use it for IMAPS (or IMAP, or POP3) and then the (relatively simple) connection in Jira to a standard mailbox?
-
Pretty much https://confluence.atlassian.com/doc/configuring-a-webdav-client-for-confluence-148044.html
-
Ok, that sounds you are talking about the function to move issues between projects, not "move to a particular status". You did not say that before. You want to restrict the landing status when you move an issue from one project to another. I'm afraid there is no function in Jira for doing that.
-
This is exactly what conditions in your workflow do. They say "if X, then do not allow transition" (most conditions are things like "current user must be in group/role or the assignee", but you can do stuff with fields and other things too) I have a feeling I may have misunderstood the question though. If conditions don't…
-
As we've already said This migration is not a supported one, and there's a good chance you are going to run into problems running JIRA 3.12 on Windows 2012. If Windows 2012 runs a very old version of java flawlessly, then you should find it works, as JIRA is only dependent on Java, not the operating system. But our concern…
-
I'm really sorry, I have no idea what Answers was doing there It posted both of my comments several times for no reason. I've deleted the repeats to try to tidy up.
-
Gary, You've had this answered a couple of times before, as part of the answers to slightly different questions you have already asked. Looking at your profile, we see a string of perfectly good questions about moving and upgrading your JIRA installation, but it really does look like you are not bothering to read any of…
-
Forget the workflow to begin with, that's nothing to do with fields (directly) The behaviour you have sounds very wrong. What type of custom field is it? Does your log have any errors or field related warnings?
-
Sort of. The status will always be visible in the workflow. What varies is whether JIRA offers a user the transition into a status. The way to do this is with "conditions", which you add to the transition - they can say things like "user must be in group X" or "field Y has content Z", and the transition to a status is only…
-
No. You need to licence each instance for the number of users that are going to use it.
-
It would be easiest to contact sales-at-atlassian-dot-com to get this sorted out. I'd start by making sure you have access to both companies my.atlassian accounts (be added as the billing or technical person on the licences), but then contact Atlassian for more.
-
There is no such gadget I'm afraid.
-
Not built-in - remember that it's an issue tracker, not a CRM system, and it's global, so a post-code checker would not be that useful to the first, second, fourth and most of the rest of the markets/countries in the world. It should be possible to write an add-on to provide it, but you'd need to find a post-code lookup…
-
It's not a workaround, it's what you're asking for. You have to have something that definitely defines what workflow to use, and in Jira, this is project and issue type (which is a lot more flexible than a lot of other trackers). I'm not actually very site of what you're asking either - if you try to do workflow and other…
-
Workflows (and most other config) is not by issue type, it's by project AND issue type. A lot of places only do it at a project level. What I'm getting at is that you can do: Project 1: Bug: Workflow 1 Project 1: Feature: Workflow 2 Project 1: Task: Workflow 3 Project 2: Bug: Workflow 3 Project 2: Feature: Workflow 4…
-
My apologies for not being able to respond in French, my language skills are sadly lacking. You do not paste licences into Cloud. With Cloud, you buy the licences through your my.atlassian account, and they get applied to your system automatically. I suspect you've bought a server licence, which you can't apply to Cloud.…