Comments
-
Oops. Expiry functions, not export!
-
You could add document properties but you won't get much benefit from that. Confluence doesn't have export functions. But, there are some very good implementations on the marketplace
-
Hmm, that sounds odd - I've used much larger installations and not seen any degredation of speed on create issues. I imagine you can override the create issue page. I would actually keep it simple and not try to override anything other than the default. If you always want to set it to "project X" (but still leave the user…
-
Not really. The problem is that Jira needs to know what the Project and Issue-type are before it can do anything else. The "components" field in Jira is dependent on Project, and not the other way around. So you can't pick a component and derive a project from it. It gets even more difficult if you remember that you can…
-
It's for mapping values, as it says on the tin. Let's say you have a select list that should contain Red Yellow Blue But your import data contains Red, red, RED, Yellow, purpli, Blue, blueish, pink - you probably want all the Red variants to be red, blue to be blue and so-on
-
It looks like you've made a significant mess of your installation. The bit of log you have shared is useful to know, it does lead me to think someone has tried to do some form of copy, and messed it up completely. All those "copy of" files look like someone has used windows explorer to copy the files and then paste them…
-
There are two types of admin on JIRA - System admin and JIRA Admin. A system Admin can do everything. A JIRA Admin is restricted to looking after the application. JIRA Admins can add you to their group, but only system admins can add you to system admin groups. You are on Cloud, so you will not get system admin anyway.…
-
For a transition button to be shown to a user, two things must be true * The transition exists in the workflow. I'm not sure what you mean by "phase", but workflows essentially have two parts - status and transitions. A transition moves from one status to another. So you need to make sure that there is a transtion from…
-
Contact "sales at atlassian dot com" direct, they're really helpful in situations like this.
-
"can not enter" does not tell us what the problem is. Can't get to screen, field greyed out, horde of annoyed penguins between you and your computer?
-
Yes. First, check the space permissions, looking for the rules on who can : * Add/Edit page * Delete page * Restrict page Next, go to the page you want to protect, and set the restrictions you need. See https://confluence.atlassian.com/doc/page-restrictions-139414.html
-
What system of page approval/authorisation have you set up in Confluence? Or are you asking how to do it?
-
You're going to struggle. Addon usage simply can't be done - many addons provide functions rather than content and you can't search for that. Macro usage can be done, sort of. There's nothing built in that will list your addons, but have a look at https://answers.atlassian.com/questions/155280 - @Davin Studer has a really…
-
Same as JIRA, as it runs inside it. Start at https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html You will find that the applications (Service Desk and Software) are quite large and do add a bit more load, so I'd be prepared to add a bit more memory or CPU if possible.
-
The question is very unclear - it's written in language that might have specific meanings in JIRA and it's hard to see what you are really asking. However, from what you've said, I think what you are asking for is: * A user creates an issue, selecting a component. * When they create this issue, you want the reporter to be…
-
Depends on what you've got in the permission scheme. For reporter, it will list people who match any rule you've got for "can create issues". If that rule is "people in the role of users, project lead and a chap called Fred", then you'll get Fred, the Project Lead and all the project users in the list.
-
No, hang on, you can put someone in a permission scheme AND a role. They're separate things. When Jira asks the question "can person A do B", it looks at the permission scheme and thinks "oh, they're named in there, so let them do it". If you haven't got them in there, then it carries on with the "no" and wanders off to…
-
Roles are defined globally, and available to all projects, but the people you put into each role is project based. Imagine you have roles like Policeman, Teacher and Paper-shuffler. Then you have a load of English counties that all need Policemen, Teachers and Paper-shufflers. Now let's take a chap called Fred, who is a…
-
Yes. The project role is just one way to grant someone a permission. Naming them explicitly in the permission scheme is another way.
-
Only the standard documentation on watchers - make sure you have the "maintain watchers" permission in the project and then click on the watchers list on the issue.
-
You can only add users to a watcher list. A distribution list is NOT a user - it's an artefact (with an email address) held outside JIRA that JIRA has no knowledge of. Your only practical option is to trick JIRA into representing it as a user - add a dummy user with the list's email address.
-
I've only ever seen that message accompanied by a huge block of data in the application log. Which file(s) are you reading for the errors?
-
Yes, that's exactly what the document Jobin pointed you at says.
-
Excellent. Thinking about it, it doesn't need to be anonymous-access really - that's just where where I first ran into the problem! The email system doesn't really know if someone can log in, it's got "this user has a valid email address, they are a watcher, and they can see this issue". It doesn't need them to log in, so…
-
It's not quite as simple as it looks on the surface, as there's a couple of things to look at. First, you've got a user, with a valid email address. That means Jira knows where to send the emails. Second, you've probably done the right thing in removing them from Jira users to prevent them logging in. Third, the actual…
-
It sounds like you are using the "comment visible to" box and selecting an option that does not allow you to see it. (Your admin rights let you do administration stuff, they do NOT let you "do everything" as that's a really bad security model - you need to make sure you are explicitly a part of one of the groups or roles…
-
It sounds like you are using the "comment visible to" box and selecting an option that does not allow you to see it. (Your admin rights let you do administration stuff, they do NOT let you "do everything" as that's a really bad security model - you need to make sure you are explicitly a part of one of the groups or roles…
-
Are you using Tempo for your "time sheets"? If so, then that has reminder functions built into it. If not, then you're going to need to think about this - Jira can send subscriptions (e.g. all my issues with no timelogs) but it is issue based.
-
Atlassian support are very good, and there's no question they'll try to help if you raise a request with them (and you have a valid licence of course).Here at Answers, we're just end-users, like yourself. There's no SLA, no requirement to respond, and it's not a chaseable support place - we're all volunteers. But... we are…
-
Yes, the worst case should be just a licence update - you may need to regenerate it if the server-id changes, but that's only a 2 minute job. If you're restoring everything like-for-like, you may not even have to do that.