Comments
-
There's two different questions here. * Permission to deal with issues reported by a specific user * Permission to deal with issues reported by oneself The first one might be possible with some torturous logic and updating user-based fields automatically as changes are made to the issue, but I wouldn't really like to try…
-
Fix your screens first, otherwise it will keep happening.
-
I think the search functions here are very weak, there are loads of answers on this subject Cause: someone has put the resolution field on the edit (or create) screen for your issues, so the users are setting it (they can't leave it blank) Fix part 1: * Go through all your screens and remove the resolution field. I * It…
-
2-5 appear to be a function of the web-server you're using, rather than JIRA itself - you'll need to look at that. Point 1 - not a lot we can do without knowing which error it is.
-
What's wrong with https://yourjira.org/browse/ABC ? There's no custom url for duplicating the landing point in JIRA (presumably because it's a generally useless function), but you can easily put in redirect pages in your web-server if you want to have a url that redirects to the right place.
-
You could take the full backup and use "project import" to import just that one project. But you will need to close the config of the project manually before doing the import.
-
Your data is going to be too old to import directly in to Cloud, so, I would * Copy both systems to temporary test systems * Delete anything you don't want * Upgrade the copies to a more recent version* JIRA 4.3 -> 5.2 -> 6.4 -> 7.0 -> 7.latest (There's a good chance you can skip the 5.2 step, but you'll need to test it) *…
-
It's not separated from JIRA - you have to have JIRA running in order to run Service Desk. Service Desk is an application for JIRA and runs on JIRA Core. So, no, your user directories are still provided by JIRA Core underneath it all.
-
Yes you can - Confluence has remote APIs. Howver, "how can we use it" depends entirely on what you actually want to do and what your other system can support in terms of remote access. On the Confluence side, have a look at https://docs.atlassian.com/atlassian-confluence/REST/3.2/
-
You can use "category = X" to find all issues in projects belonging to a category and "project = ABC" to find the issues in a project. Those can be extended to "in" statements (like "project in (ABC, DEF, GHI)"
-
You'll need to find or write a service that can run a regular import, after checking that incoming data actually needs to change. This isn't going to be easy, unless you've got a very simple flat file format. I would be strongly tempted to run it externally too - write a script that can interrogate any issue that is going…
-
I know. But it does get the configuration without you having to process the XML. Combined with "project import from full backup", it's the closest you will currently get to "copy whole project"
-
You can't. JIRA does a full export of everything, and you can import the issues from one project from that. But that's it. If you need single project backups with configuration, you'll need extra functionality. This is exactly the case where I would reach for Botron's tool…
-
That's not what the system is telling you, although you've misread what I said and got it the wrong way around. Your Confluence is not configured, as it believes it needs to set up the database, but it's trying to connect to one with data in it. So it's complaining because it doesn't know what you want.
-
No. What you're doing is trying to connect an unconfigured Confluence to a configured one. It cannot know whether you need to go through the setup again or not. Your next step should be to connect this Confluence to an empty database.
-
Technically, you can get sprints on multiple boards, so no, there won't be an easy mapping...
-
Yes, your requirement is very clear. It's not going to work if you try to do it this way, but it is clear. The Jira database is actually pretty well designed. For being the storage engine behind Jira. The main problem here is some dodgy reporter application that can't and won't keep up with the data structure that is…
-
There is no direct relationship. A board works off a JQL query. You'd need to find and replicate that query in SQL to be able to say "this issue is on this board". In other words, read the Board table to find out what the filter is. Look that up in "searchrequest", read the query in there, converting each clause and join…
-
Start at https://confluence.atlassian.com/display/DOC/Working+with+Templates
-
No, it might be valid for the issue. For a field to appear:It must have the right "context" if it's a custom field (see the list of custom fields)It must be on the screen you are looking atIt must not be hidden in the field configurationIf you are looking at the "view" screen, it must have data in it, or JIRA will quietly…
-
I'm afraid you have to work it out from the context and config Note down if you are in the Create process, an Edit process, looking at the issue view, or, if you are part way through a transition. Go to the project header screen and look at the settings If it's one of Create/View/Edit, then go into the "issue type screen…
-
You said it yourself - "because Service Desk agent overwrite this permissions"
-
Service Desk projects need an additional layer of permissions and rules within their permission scheme in order to handle customers and agents correctly. What they do, why and how is an essay question, and not one that I'm qualified to write, but I can tell you the simple way to handle it - have one or more permission…
-
There's two questions here. First, don't use SQL to change the base url. Change it in the UI under general configuration, and if you have application links between them, go into them and edit the urls in those links Second - redirection is NOT the same as changing base urls. If you have users landing on your old defunct…
-
No, you just need to edit the condition(s) on the "close" and "resolve" transitions, OR change the permission schemes. The transitions will have something like "user must have resolve permission" on them, so by editing the permission scheme, you can determine who gets the permission. Or change the workflow conditions.
-
You've misunderstood what this is. The plugin *is* for the mail client, as I said already.
-
I'm not sure I understand the question. * JIRA sends mail via a mail server that you configure on your server. * JIRA can fetch mail from mailboxes and create/comment issues from incoming mail (it can do more if you code or find add-ons like JEMH to to more clever things, but it's all based on "monitor mailbox, act on…
-
FTP won't really work either - even if you upload files to Confluence's attachment storage, it won't attach them unless you do a stack of scripting on top of the transfer.
-
Planning is for prioritising and deciding which stories go into a sprint. Subtasks are part of stories, so they follow their story into a sprint. If you have multiple teams, that's fine, and sub-tasks are a good way to break up stories into pieces that can go out to different people. But your teams are working on one…
-
Er, it's nonsense to plan sub-tasks outside their story, so they don't appear in planning.