Comments
-
You need to take a look at your permission scheme - the users need to have "resolve issue" permission. And it needs to be on screens.
-
You can't put conditions on the create issue, because it doesn't make any sense. A condition works on a data set to work out whether you can perform a transition. When you are creating an issue, you don't actually have any data to work with. In other words, the condition would have to magically know what data the user is…
-
What do you mean by "report"? A Report in JIRA is a function that displays some information from a project or filter - the users do not create these, they just run them. So, you might mean "a report written as a plugin and installed by the old user" in which case, an admin can delete it from admin -> manage addons. Or you…
-
Yes, you can use Connect add-ons with Cloud, and any of the addons Atlassian are prepared to support - check the marketplace or your my.atlassian account for what you can install.
-
Ooops, thanks CharlesH, yes, I should have said that pages have to be uniquely named *within a space*. You can have lots of pages called FRED in your confluence, as long as each one is in a different space.
-
Ok, but the answer is the same - no, because you could not know which page to serve up if there are two with the same name.
-
By "site", do you mean "Confluence space"? If so, then no. You can create links and redirects that all point to one place, but you cannot have duplicate space names. How would a browser know which one you meant if you had two?
-
By "site", do you mean "Confluence space"? If so, then no. You can create links and redirects that all point to one place, but you cannot have duplicate space names. How would a browser know which one you meant if you had two?
-
The p4info tells you that it can connect, and hence rules out a number of problems, but that's a short and simple connection. You always need to run it. In the original question, that was simple - the network was not allowing JIRA to reach the Perforce server, but you have a more complex problem - the server is killing the…
-
Can you check what "p4 info" returns when you run it on the JIRA Server as I asked before?
-
That's simple - your JIRA service is running on a machine that does not have access to, or cannot resolve the name for, your perforce server. Can you run a perforce client, or even just "p4 info" on the JIRA machine and see if that can reach it. I suspect it won't, and you'll need to work out why and fix that.
-
Yes. See https://www.atlassian.com/git/tutorials/making-a-pull-request/ The server version of Bitbucket is pretty much the same as Cloud, but has a bit more flexibility in some ways. Pull requests are fully supported by both
-
Not off-the-shelf. The only fields that use a shared list are the version type fields (affects, fix and then you can add other version custom fields) You'll need to find/write a custom field type that can draw values from a single list for multiple instances. Personally, I'd just use versions in this case - add custom…
-
Or just don't mention project at all in the query. As all issues belong to projects, your clause is totally redundant.
-
That's not really possible. Jira's search finds issues. Not versions. So you can find issues with unreleased versions, but not the versions themselves. Two tricks though: 1. Use the advanced JQL search, and look for the "help" icon. Then look for JQL functions, and if you're on a later version of Jira, you'll find…
-
Yup, just leave out "project =/in"
-
That is what a "cascading select list" field does, try adding one of those.
-
That does not sound right to me - when you change a workflow for an issue type, all that should change is the workflow. Could you look at one of the affected issues, click on the "history" tab and look at the exact changes made when the workflow changed - is the workflow change grouped with the reporter change?
-
>how to wrap them? In the html/vm you have to put in to enable the panel - that should be obvious! I also should say I totally agre with Jamie - I hinted at it in my original answer, but I worry that you're wasting a lot of time making things more complex and less flexible by adding duplication that you'll almost certainly…
-
Looks like Atlassian have been reorganising their Confluence - the page I was looking for is back - http://confluence.atlassian.com/display/JIRADEV/Web+Panel+Plugin+Module - I'm not sure that's exactly what you need for my 3rd suggestion, but I think it's close.
-
The "simple search" panel already has functions to allow selection by status, so adding buttons there is needless duplication. (Or, you might want to just throw it away completely and write your own way of doing it less flexibly) If you want to add panels like this in other places, it's not too difficult. I would advise…
-
vi, emacs, atom, sublime, any half-way decent text editor can chunk up large text(xml) files.
-
Nice - I'd not spotted the duplicate flag before.
-
The Jelly create function won't let you create an issue with a duplicate summary. You need to vary the summary of each new issue. (I assume you are trying to automate some regular tasks - if that's true, you should be able to use a date function in the script to get a unique date inserted into the summary)
-
Components are offered as a field on issues during create and edit, so you just select the ones you want on an issue. If you're missing the field, check screens and field configurations.
-
Not really. Components belong to projects. You could try to wedge in a spot of javascript to remove components from the selection lists based on the issue type, but you'd still need the full list at the project level.
-
There's a button on the sidebar to toggle it, next to "space tools". The << and >> That's in the standard theme though - if you're using a different version of Confluence and/or a different theme, it might not be there, but it might be possible to add it. But we'd need to know what we're working with.
-
I'll shut up about that bit then :-) I might be thinking about raising this with the authors though - if you've got the right versions and the plugin still doesn't seem to be loading correctly, I think it might be one for them. I'd check the logs from Jira startup carefully though - does it say it's loading and starting…
-
I'm not sure about the actual issue you have with the plugin, but it looks like the plugin is partially disabled - can you check that in the plugin section? Look at the plugin and all it's modules. If it's enabled and you try it again, some plugins can become disabled if they fail while running - that might tell us some…
-
From experience, I would strongly recommend * 3.4 -> 3.6 (there's massive changes in 3.6 and going past it in one hit caused me no end of problems every time it was tried) * 3.6 -> 3.13 (If you have problems here, then make more steps - go through 3.8 and 3.10) * 3.13 -> 4.4 (again, if you have issues, drop to 4.0 then…