Comments
-
The "all" type transitions have the name of the status that they go into!
-
Darth is doomed - he's got a waterfall project to defeat people being Agile...
-
I would look at the various test management apps in the market place, although you would probably only need one of the lighter ones.
-
The descriptor url is the url of the app you are trying to install. How are you trying to do this "install"?
-
Model for what? You should probably be building your own model to suit your reporting. Sorry, that was a little short, I hit send too early. I'm currently building a reporting-on-jira database model. It's totally different to a Jira database structure, because the Jira database is not built to be reported off, and it's not…
-
Welcome to the Atlassian Community! Have a look at the board configuration, and check out what status are mapped into the last column on the board. Let's say you find "done", "closed" and "cancelled" as three status in that column, and your board is a simple "project = XYZ" board, then your query is project = XYZ and…
-
There's nothing we can help you with here, I'm sorry. You need to talk to the administrators of that bp system, and we can't know who they are (nor who Aravo is)
-
You've tagged this with "Cloud", where you have no control over upgrades, nor any need to do anything about them. If you mean Server/DC, then as long as you are using a standard supported Atlassian upgrade on it, then no, it will handle all your config and data for you, and you don't need to think about it (unless the…
-
Yes, those buttons are triggers for the transitions. You have loads of transitions in that workflow. The arrow between "all" and a status is a transition. The "all" just means that the transistion starting point can be any of the status in the list!
-
Welcome to the Atlassian Community! At it's heart, Jira is an issue tracker, and an issue can represent anything you think of as a "work item". It's quite likely that you can translate your excel data straight into Jira, each row being an issue and columns becoming fields.
-
Your errors are clear - those fields are not configured to be used on the request type you are trying to make.
-
No, Atlassian applications do not use arbitrary attributes for access, it's done on groups and individuals.
-
Welcome to the Atlassian Community! You do not. You check the project's permissions to see who they say have "Edit issue" permission, and then you change that person's roles/groups/settings to match the rule. This gives them the right to edit all the issues in the project.
-
So reporting then, but based on data you extract and transform. Best thing to do is read Jira over it's REST API to get the data you want to put into your reporting database/tool.
-
Welcome to the Atlassian Community! Epics really only have an overarching workflow of To-do -> In-progress -> Done, but you can give them whatever Jira workflow you want as well. The to-do, in-progress and done steps are more generalised meta-status, but they have some simple rules which I think you should consider…
-
Yes. If a user cannot see an issue, then they can't see any of it. Links to it will not appear on issues they can see, it won't come out in searches, and will not be accounted for in reports Imagine you've got 5 issues with the same priority, and I can only see three of them. We share a dashboard with a pie-chart done on…
-
The licences are applied to the subscription or server, not the individuals. My Adaptavist Atlassian account has access to maybe 50 Cloud Jira systems, and it consumes one licence on each of them. It's a little different if you have an Enterprise agreement - the individual in the organisation does get a single licence to…
-
Yep, you'll need Scriptrunner (or one of the other apps that can effectively nest searches) to do this. Thanks @Marco Brundel !
-
Welcome to the Atlassian Community! Could you give us some more context? Is this an error message? Where are you seeing it? If it's not an error message, what are you doing when you are "reading fields from the table"?
-
Welcome to the Atlassian Community! It was one of your site administrators, you'll need to ask them who installed it (and why, presumably)
-
Welcome to the Atlassian Community! I'm afraid Atlassian can't help you with a lost Google account. It sounds like you probably need to look at recovering your Google account - https://support.google.com/accounts/answer/185834?hl=en is a starting point I think
-
Welcome to the Atlassian Community! Everything needs to be considered for a migration up to the Cloud. Cloud is fundamentally different to Server and migration is quite a hefty data migration Start with a read through https://www.atlassian.com/migration/plan/cloud-guide#migration-tools However, I would make two points…
-
Welcome to the Atlassian Community! Your first query makes sense, you're asking to see all the stories in the project with no due-date. It's not going to show you any sub-tasks because sub-tasks are not stories. Can you explain "does not work" for the second query? I would expect that to return all stories and sub-tasks…
-
Could you try this with a different browser, one with no extensions or special configurations added?
-
This sounds like an inexperienced admin has added a custom field called "assignee", something you should never do. If this is a company-managed project, an admin should go to Admin -> Issues -> Custom fields, find "assignee" on the list and rename it to "not the assignee" or something. For a team-managed project, it's…
-
Your "design" is a bad one, I'd suggest fixing that instead of botching something with code. Automation can't help you with this, you'll need to write code that can validate the field and either tell the user they've entered junk, or take a guess at what should be entered. If you used issue links as intended, you wouldn't…
-
Excellent, that's a couple of steps forward from my "and issuetype". I looked at issue type to try to illustrate why stuff wasn't coming out in the context of your starting point. Project and parentEpic is a far better way to do it here!
-
Welcome to the Atlassian Community! What do you mean by "import"? You can easily attach a spreadsheet, like any other file, and if you do that, you can also use macros on a page to extract data from the attachment for display in the body. But I don't think I know what you mean by "import"?
-
Welcome to the Atlassian Community! Short answer is "no". The way an issue works is determined by the project it belongs to. You can't manage issues outside a project - they have nowhere to be configured, so they wouldn't be of any use to you!
-
Ah, that's an oddity in Jira-speak. You do not actually select a status, or even edit it. Status is not a field, it is a display of where an issue is in its life-cycle. You change between status by using one of the outgoing transitions associated with the current step (status), which, in some places, looks like a…