Comments
-
I'd say it sounds like a good case for a new project. But it very much depends on how you want to run your teams and project work. I would be tempted to leave the current project open for maintenance fixes, and have a new project for the rewrite, as it's probably a separate bigger peice of work. I doubt the people doing…
-
Users and groups in projects are only part of what you need to look at. You need to cross-reference this with the permission scheme for the project. This will say things like "project lead and role X can admin the project", "role Y can edit issues", "role Z can create issues", "everyone in group jira-developers can see the…
-
Yes. JIRA's workflows are usually best mapped with a simple flowchart. I'm not clear on what question you are asking here though, could you explain?
-
Sorry to throw you over to another site, but if you're having problems accessing a Cloud account, we can't really help you, you need to talk to https://support.atlassian.com directly.
-
Totally different things, although you will end up with the same system if you follow the steps correctly. * The easy way to imagine this is that * You have a database that acts as JIRA's data store * You can copy that out as a dump, suitable for your flavour of database * You can use JIRA's backup routine that reads the…
-
It sounds like your user doesn't have the global permission "create shared objects". When you add him to an admin *group* (not role, that's something different), he gets it because that group has it. You should add them to a group that has the shared object permission but also does NOT have admin.
-
There is no such thing in JIRA, and there's no add-ons I can find that do it either. There are add-ons which provide extra layers - look in the marketplace for Portfolio, Big Picture and the other PPM things. But sub-projects just don't make sense in JIRA and pretty much don't happen.
-
So, this is an add-on for Confluence that provides a macro? From memory, there should be a "context" variable, which gets an id via context.entity.id
-
The video shows the use of a CSV file, so I'm a little confused by the question.
-
You could also try raiding a Summit or AUG if you only need a couple - there's usually loads available for free there.
-
Adding a watcher to an issue does not send an update itself (although that is a popular request open with Atlassian)
-
The answer to that depends on where you are starting from! Imagine asking someone "how do I get to London?". When they don't know where you are now. Where is your code running basically? A script? A user macro? A search result function? An add-on that's adding some form of interface (like the admin fuctions)? Another way…
-
I think you are still missing the point. A board is a view of a set of issues. They don't have status, they draw them in from the issues they are looking at. Issues do not belong to boards. A board has a filter which selects issues. If you want an issue to appear on a board, then you have to set up the board to select it.…
-
Ok, you need to re-read ALL of my comment, not just the first line.
-
No, your query is utterly wrong. This is *exactly* one of the reasons you should not be using SQL to read it - you don't know how to read the database at all. I'd say whatever your plugin is has the same problem. Custom field data is held in customfieldvalue.
-
As I said, I can't add to that.
-
No, the whole point of the search and display functions is that you can see any of it. You could remove the "searcher" for a field, but that makes it completely non-searchable The best thing you can do is sort out your "fielditis", rationalise, consolidate and simplify your field list, not try to bodge the display.
-
Could you give us * What type of Board this "jira board" is? Scrum, Kanban or Business? * If it's Scrum or Kanban, the board filter * If it's Kanban, also the sub-filter for done * What results you get when running the main filter in plain JIRA and what part of the board is showing fewer or no issues - plan or work mode if…
-
The "configure fields" function is a personal setting for each user which does not look at the settings like that, it's agnostic of the other settings, reflecting what the user has selected in the past, irrespective of the setup of the particular issues.
-
You say "To do so, we need some basic information about the application (like in which it is hosted and all aconfiguration items etc)". Neither we, nor Atlassian support, can tell you any of that. It's your system running on your servers. But, try looking at the "system information" page.
-
Yep, I can't add to "project in (x, y, z)", it's right.
-
You mean Confluence "Cloud" - it's not been "onDemand" for several years. As it's Cloud, you don't have access to the logs. As soon as you get anything that says you need access to logs, you should go straight to https://support.atlassian.com - it's their job to investigate and fix Cloud system errors.
-
Run a filter that selects the issues, then use it in something like the issue navigator - you can select priority, owner and components as columns there.
-
You probably need to explain to the audience what a "greenhouse" is.
-
Boards do not live within projects, and issues do not live within boards. They are not "moving" from one board to another. The data on the issue changes in a way that one board deselects them and the other board now includes them. A board is a view of a set of issues. You simply need to work out what you want your boards…
-
The url I've already given is correct, but Atlassian seem to have a website issue at the moment. Give it a few minutes.
-
Managing users. It's in the document.
-
https://confluence.atlassian.com/adminjiraserver072/assign-users-to-groups-project-roles-and-applications-828787671.html
-
No, there's no gadget for that, you have to do it all with saved filters.
-
What spam? You'll need to explain what you're getting and where you're seeing it.