Comments
-
Depends on what you were backing up and how. This is probably something that should go to the server system owners to ask.
-
Interesting use of a Space Station Information System, but hey, NASA got robots to Mars using the Atlassian stack ;-) I'm assuming you are using some form of database query. To keep this simple, this is generally a very Bad Idea (tm). A JIRA database is absolutely not designed for any form of direct database reporting and…
-
There is no "feature" level implemented in JIRA Software. There's an add-on which sort of enables it, as long as you're careful with the config of it - the "Structure" add-on is well worth a look.
-
You can share a filter with someone and they won't be able to change the filter. Nothing to stop them copying it and changing the copy. The goal has nothing to do with filters though. A filter looks for issues and that's it. If you want to hide issues from a user, you need to use either project security (make sure the user…
-
There is no project export. Your question was about importing, not exporting, so I could not know what you were really trying to do. Your options for that are: 1. Import the project you need into an empty JIRA (you'll need to manually recreate all the fields and config. OR import the whole thing into an empty JIRA and…
-
I was thinking more of any "behaviours" - do you have any of those in use?
-
Yes, you're right, 12 in a row would be a nightmare! The looped transitions that set things probably is the most useful in that case. The basic idea is what you've suggested. The workflow would contain a step like "needs authorisation". You then put a transition from "needs authorisation" back to "needs authorisation" on…
-
Projects don't have a status, they're just containers for issues and their configuration. There's no concept of project status. A couple of simple options though 1. Look in the marketplace for the Portfolio management type add-ons (Portfolio, Big Picture, etc etc) 2. When creating a new project, have issue #1 be a "project…
-
Ok, have you tried adding the versions to the card layouts?
-
summary, parent please make tea, ABC-1 please make coffee, ABC-1
-
Hmm. Does export to CSV on Cloud do much with empty fields?
-
Not sure I've seen a write up of it directly, but it's not too hard to do. You basically create an account that is in the admin group(s) set up in the global permissions, and then make sure none of your spaces include any of the admins or admin groups in their permissions. An admin will always be able to grant themselves…
-
The Greenhopper API has been heavily reworked and had swathes deprecated as it evolved into JIRA Software. I haven't tried to code anything with WorkingDaysService, I'd head over to the developer community to ask there.
-
No. A portal sits in front of a project. If you want to create issues in none-service-desk projects, your user needs to be a full JIRA user.
-
I don't think there is any value in videos of people clicking on a few buttons. * Go to Admin -> Backup manager * Click the backup button * Wait until it returns to a "done, and here's your file" page * Click the download link And that was the *long* version.
-
Forget the "customise fields" thing, it is not relevant to the question here. The customise fields option is for the current user only, and it allows them to choose what fields they have on a screen. You, as the admin set up the screens, and you, as the admin, don't really care if they choose to hide some fields from their…
-
Nor can I, the JIRA 7 docs seem to have lost it (along with a lot of other useful stuff)
-
What you call "autosave" is the whole point of inline editing! It saves what you change without having to go into an edit screen. Alex's solution of turning it off is the only option.
-
I'm not sure that your description is clear on what you are doing. The first paragraph makes sense - you want to move a Confluence from one server to another (see https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html ), and later upgrade it as a second step. But then you say something about…
-
Bear in mind that boards do not belong to projects, and projects don't belong to boards, so there's a good chance "board admin = project lead" is not a valid choice. There's no easy way to get a list of all the admins, the best you can do is seeing the list of boards with their owners listed.
-
That would suggest a resolution has not been set on the issues going into that status.
-
The backup Cloud generates is a one-off download of a block of xml that can be used to create another Cloud system or import into an existing JIRA server system if you want to move off Cloud. As you say, it can only be generated once every 48 hours. What should have happened is that you were taken to a page with a download…
-
You will need to write a JIRA Software add-on to duplicate that functionality. The Epic link is not a field type, it's a linking system built into the core of JIRA and JIRA Software.
-
Ok, thanks for the clarifications. It does seem like the whole of this seems to be down to the simple "you must be in the group or project you are going to share with" rule. Can you put yourself in the right groups and roles and check that you can now share as you want?
-
The best version to use is the 2.1.17 you found. 3.0.7 might have been installed manually, but I wouldn't recommend using anything other than a version that is officially flagged for that version of JIRA. Your licence covers you for all versions, so I wouldn't worry about that, although 2.1.17 is a free version and doesn't…
-
Two options 1. Find or write something that can read a remote JIRA and display it in the current one. This isn't too hard, as you can scrape a JIRA over REST and build something to display things. Massive downside is that the data is still on the remote JIRA, your local one doesn't know it's JIRA data. 2. The proper…
-
>as an admin I have unsuccessfully tried to change the ownership of the board Could you explain what happened when you tried to do that? The errors or behaviours we see there can tell us a lot more about the root problem. The bug you've found does not affect your version of JIRA, so it's not that. Two things on this line:…
-
You don't get "sys admin" on Cloud. The backup option remains available to Confluence administrators, as that's the only route you have of getting a backup.
-
Your fears are perfectly reasonable, but probably unfounded. Atlassian tends to separate out "use" from "admin" quite strongly in the permissions. You can have an admin account that can't see any of the content, let alone amend it, because their job is admin, not user (and obviously a user has no admin access). Working…