Comments
-
Permissions are done at a project level in general. You can overrride permissions for issue types, but it's not an easy job - you have to create a workflow for each type of issue you want to have different permissions, associate them with issues in the workflow scheme, and then use "workflow properties" to alter the…
-
Absolutely, otherwise your urls in the emails and links are broken, not to mention reporting and other stuff. Our system: Confluence runs on a host called server011, presenting SSL connections on port 8999. The url https://server011:8999 is the base address, but is actually only accessible on that one server, the port is…
-
Change the base url in Confluence to be consistent with the one Apache is presenting to the outside world.
-
That's not right - Linux generally stops you from using ports below 1024 when you are *not* root. Your best option is usually to put a proxy web-server in front of JIRA, as you certainly do not want to run the service as root, and the tricks to get it to run on a port below 1024 when not a root user are, well, not pretty.
-
You need to work out what else is already running on port 80, stop that, and change the port for Confluence back to 80 in the server.xml
-
Sorry, I wasn't of any help really If I do find anything to help out on Cloud (got a bit of a Cloud project next week which might uncover more stuff), I'll keep this one bookmarked so I can add it.
-
A couple, but the ones I have bookmarked are not available for Cloud, so they're of no help to you, sorry.
-
Yes, I asked which add-on was providing the module in my first response. From memory, that module is not enabled for Cloud instances. I seem to remember seeing a reason why, but I can't remember what it was. You'll need to find another way to do this I'm afraid.
-
What about the one I asked about?
-
In your question, you showed a screenshot of a couple of modules. You'll have had to have gone into the parent add-on to get that - modules live in add-ons.
-
That looks like it is enabled to me. Could you check "manage add-ons" though and see if you have the parent add-on bought and enabled?
-
So which fields from C are missing from the move screen?
-
What happens if you try to edit an existing issue of type B? Does that bring up the correct fields? Also, what happens if you enter all the data into the "wrong" list of fields and commit the move?
-
You can, yes. But, bear in mind that you will need to restore back to the database backup (or xml if your instance is small) that you took before you upgraded to 7.3
-
Ok, are they the current assignee then? (You have ruled out "watcher", so I need not ask)Next, have a look at all the assignee and all the watchers on the issue - are any of them maybe group accounts? Check the email address for every one of them.
-
If you've removed reporter from the notification scheme, then they are being notified for another reason. Look at everything you have on the "issue updated" event (I'm guessing that's the email your reporter is getting). What other groups/roles/functions might they match?
-
Kanban boards are not "under a project", they select a set of issues based on a filter. To associate tasks with them, you need to make sure the filter for each board includes the tasks you're raising for it.
-
Ok, that doesn't sound right. If you go to admin -> system -> security -> project roles, what do you have listed?
-
You're nearly there Your role will now exist in all projects, so the next step is go to your project and look at the "permission scheme". You probably want to edit this so that it says "Browse: role(external)" and the same for comment. Then, go back to the project and add the new user into the role of "external"
-
It's only hard because the defaults are poorly implemented. You have to remove his access in general, and then let him in to only the bits he should see. The default setup in JIRA is based on the unfortunate and usually wrong assumption that users will need access to everything, and you have to unpick that setup before you…
-
None. Atlassian do not support clients running server directly. They'll do support when you're stuck, but not run the system for you - you'll be responsible for upgrades, patches, backups, DR etc. If you want Atlassian to run the services for you, then you need to adopt Atlassian Cloud on their platform. Some Atlassian…
-
You can't change it, it's coded and you can't change the code on Cloud.
-
If you are creating a new JIRA system, you need an empty database for it. Specific questions: * Under no circumstances should you point two JIRA installations at the same data set (JIRA data centre is a different case, I'm just talking about plain JIRA). It's fine to have several JIRA datasets on one database server, but…
-
The tabs are purely display things. Containers for dividing up field displays. The data for the field will not be touched at all. You can safely delete a tab full of fields, then add the fields back on to another tab, and you'll lose nothing.
-
Er, you need to look at the urls you're using. Your REST call is not going to the ASF system.
-
What is an ASF JIRA? More importantly, what version is it, where is it running and what are you actually trying to do here? A simple search for "project = pig" will get you a list of issues in the project
-
So what do the contents of your 3 groups add up to? Also, could you check what Admin -> Licence says about the number of users?
-
I suspect you need to check this with raw data. Go to Confluence Admin -> Global permissions and check exactly what groups have "can use", AND "administrate". Add the groups together and de-duplicate. I suspect you'll find it comes out at 100.
-
I'd agree with your overall opinion of the Epic - you'll note that I didn't say that they were useless. Just that the Epic report doesn't make much sense for Kanban. Because it's designed to report on Scrum based activity, not "drinking from the firehose". No, I don't represent Atlassian at all. I work for one of their…
-
Epics don't really make any sense for Kanban. Kanban boards represent work arriving (hopefully in discrete packages, represented as issues). An Epic is an overarching idea of a piece of work that needs to be broken down into pieces across many projects. That's simply not what Kanban is for. One of my old PMs described it…