Comments
-
What do you mean by "archive"? The answer is very heavily dependent on that, and is almost certainly going to lead you into rather a complex project that you'll need to plan very carefully. Think about these specific questions: * Is there an easy way to identify everything to archive? (e.g. resolved and last updated <…
-
Yes, up to 15 minutes, plus the time it takes to run the indexing on the repository.If you have configured it as per docs, then the next question is "what does the log file say"? (In JIRA)
-
Follow the instructions for using it? Set up the link to subversion in the plugin config screen, then let it build an index from your repo.
-
Start with https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.subversion
-
Ah, sorry, I didn't notice the "Cloud" tag, sorry. I'm not familiar enough with Cloud to know where the location is set byb default. I've seen Cloud use localised dates, so I know it is possible. I'd check the user profiles and defaults to see if you can tell it where you are, so it will use local date/time
-
Best guess is that your operating system and/or java locale settings are pointing to the wrong time zones Have a look at the system information page to start with.
-
It's the admin and maintenance stuff. If you were to move one of your issues into a sprint, other board-admin users who can't see it wouldn't be able to close the sprint.
-
Yes. If you set up the permissions on your personal project so that only you can see the issues in it, then the issues will not appear on the board when other users are using it. However, you will need to think through the impact on board admin though - users will get "can't see affected project" if they try to do some…
-
The dashboard login is actually a gadget, so it's bundled up into a "system" add-on. You'd need to upack that, hack the templates and rebuild it. Possible, but ugly, and a lot of effort. I'd take a look at why people feel the need to click "not a member" first.
-
For what it's worth, I'm with Rahul and Andy on this - dropping any tables out is asking for failure. You need to understand what they all are before you try anything like this, and even then it's likely that the simple rule is that you should take everything, exactly as it is now.
-
You could try to write a condition that looks at the current status. That would do it. I'm not aware of a plugin that provides one - most people do it with non-global transitions
-
Why do you keep saying NIC on your questions? If you want a workflow that doesn't do "all" then remove it and add the transitions you actually need.
-
Pretty much answered that yesterday - see https://answers.atlassian.com/questions/38517166.
-
It sounds like you have the wrong status in your columns - the "done" column should contain the ending status for the Epic, but it sounds like you've got it into an end status before it hits the done column. Have a look at the workflow for the Epic - the workaround is that you could remove the "do not allow edit" property…
-
You'll need to edit the core code that provides this message - it's pretty much hard-coded. Also, I'm not sure that the page actually gets the "why you can't log in" information in that detail - it might not be told whether the user has been disabled, been locked out, doesn't exist etc
-
Jira does not support putting a field on screen more than once, which is correct for data entry fields because you should never give a human two entry boxes for the same data item - field entry should be unique. Could you give us a bit more detail on what you are trying to do, why, and what's going wrong? Screenshots would…
-
Yes, the permissions are additive. If you add a user into the user side, they can see the project. If you add a group to the role, then all the users in that group can see the project.
-
Possibly, but there are only a small handful of things you can do on Cloud for that - webhooks really.
-
Susan's point is valid - while you can't install assorted addons that might have specific and dedicated connection routes to other systems, JIRA Cloud still implements the JIRA REST interface, which other systems can use to talk to it. So, if your other system can be persuaded to make REST calls, it can "interface" with…
-
Yes, you can. Go to admin -> events and add new events. They will then appear in the notification schemes and you'll be able to select them from the "fire event" list when you're editing workflow "fire event" functions.
-
Look at the workflow to find out what "event" is fired when an issue goes from <something> to Done - it'll be in the post-functions on the transition(s). Then go to the notification scheme and make sure the CS team is included in the rules that send mail on the event(s) you find.
-
Duplicated by https://answers.atlassian.com/questions/38839635 but there's more information on that one.
-
It's not a "security level" really. To make someone an admin, you simply add them to one of the groups that says "these people are admins". You have to be an admin in order to do it of course - only admins can make other admins.
-
It sounds like it might be easier to approach this from the other end. Could you go into Admin -> Global permissions and list out every group and person who has a tick in the "create space" column. Then, look at the user who is getting the option, and list out their groups...
-
You don't. The permission is inclusive, not exclusive. You allow groups X, Y and Z to create spaces. To exclude someone from creating spaces, you have to make sure they are not in group X, Y or Z. Rambanam's link is the one to follow for the details, but you need to think about your group structure. Most places simply…
-
Have you considered using Page Properties ?
-
Sorry, you've misunderstood - I mean you should have a project for the internal stuff and another for the external, because you can't restrict users by issue type.Service Desk doesn't actually do the different issue types, it hides JIRA complexity from the customers and makes you map issue types internally.
-
Your second solution is not really going to work. Users will be asked which issue types to create, they'll be able to see other stuff in the project that should be internal only, unless you do a lot of config work and use post-functions to set things for them. The question you've found is a good guide, but ONLY where you…
-
Ah, good, that covers the licencing I reckon. I'll not ask if you're in an auditable industry ;-)
-
It's pretty much as above, there's no locking mechanism, but there's a couple of workarounds, like restricting edit to current assignee or moving all the edit rights down into the workflow. As an aside, you say you're using group instead of user names? Does this mean shared accounts - people logging in using the same…