Sergei Gridnevskii Rising Star

Wow your parents called you a flower. 

Maybe, but when I changed category to Green the dashboard widget stoped showing Done issues. It may be a coincidence, but I still think that issue should be in final status to be filtered from the widget. I do not have index, it is Jira Cloud.

By the way I still think there is a bug here. I have an employee with Assigned to me gadget that shows 26 issues for him of which 24 are Done with Resolution set to Done. When I search in filters window with this JQL project=ITOPS and assignee = 557058:bc8b32f0-a1ee-451b-a1bb-78dc09bd1e76 and resolution is empty those…

Thanks, Mark

I got the same error recently, have no idea what it means. The rule does not complete to the end, it did not do last action.

You may start a trial Jira for free and test in for 30 days. Most functionality is covered by wizards and you will be able to form your opinion with no difficulties. I think the best option for you is Jira cloud. When you get used to it you may have Jira server on your hardware. The benefit is that you can change virtually…

I guess he needs to post issues to Jira from his app.

You can do almost everything and even more using Jira REST API. You can start from here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

I do not see the new home page yet - just a normal page without my profile icon, Recent and Spaces tab. Perhaps I am in the B group for A/B testing.

1. OK, but component is not a platform. Component is a part of an application like a DLL or a service. A component can be the same for iOS and Android, e.g. business logic in Xamarin. 2. I think it is a standard functionality, no need for post function here. 3. So in case admin is on vacation users cannot do anything.…

Component is good but he needs to be a Project admin for that and filters are a little bit more complex than just searching for text

The easiest way would be to add platform tag to Summary, e.g. ios: Button is grayed out Now you can sort issues in Search window by summary or filter them using text ~ "ios:". If you later decide that you need components or a custom field - just filter them and Bulk Change.

Thanks. Bill. I had a task to separate tickets having exactly 2 fixVersions. If you are interested, we have 2 products that are intended for different markets. 90% of code is the same. If a bug is found, it is fixed in "common" part of the app, but we still need to test solution in both products for possible regression. As…

Take a mouse and click a button

OK, I managed it myself {{issue.fixVersions.last.name}}

I don't think this solution is good. 1. It requires a paid plugin while Jira cloud already has Automation for Jira 2. Clones link can be added both by Jira and by a human. E.g. developer starts working on issue and finds out that it is a clone of another issue. He puts a link and some fields are cleared. That's not what he…

High hopes

That's why we use Insight with dictionaries for such forms. It is easy to tune up a separate filter for each issue type.

This is what I have for tech support This form is used for onboarding

I use Insight for dictionaries and custom fields in service desk forms. It looks nice and allows filtering. Also I can use same issue type for dozens of different requests, that's nice. The only drawback is that I have to create hundreds of custom fields and Atlassian adds them by default to all field configurations. If…

It can be some kind of a browser plugin that detects that browser is on Create issue view and adds some text to Description field automatically. I guess it will be very valuable for QA. Anyone volunteers to create the plugin for Chrome?

There can be different situations where adding a new plugin is not possible. Mentioning a few: 1. Team is not the owner of Jira instance and cannot install plugins 2. Budgeting considerations. For me it's a shame that Atlassian charges per user basis even if plugin is used by 1% of users. 3. UI becomes slow and issue view…

As far as I know it is not possible. But you can try these workarounds: 1. Create issues using REST API and any programming language like Python (or even curl). You can then fill description in your script 2. Save template as a word file and paste contents to new issue view each time. This is a way our QA team works 3.…

For the side questions. We use premium features a lot, e.g. Advanced Roadmaps and Insight. They work(ed) really slow if there are more than 5000 issues or 1000 objects. So it is a good idea to remove unneeded items completely or at least transition old issues to Close state. Also an issue page rendering may be slowed down…

Does not make sense if he has 100 tasks - just a waste of time.

I confirm. Export everything to Excel, clean unneeded fields, save as Unicode CSV and import back. We prepare test tasks for one of our projects this way. Analytics create tests in Excel, I combine everything in columns Summary and Description, export to CSV and import in Jira. It is pretty much straightforward.

I disagree and think this is not the correct answer. As far as I understand Vanessa means that first designer works on issue and then QA checks his result and closes the issue. I conclude there should be a special workflow with steps made by designer and steps made by QA. For each of these steps we can assign appropriate…

Yep you are right. For this particular situation of Vanessa I would create a special type of task, make two obligatory custom fields (Designer, QA), make workflow steps "In design", "In test" and make two rules that will assign the task to Designer field value when it is transitioned to "In design" and to QA when it is…

When I have issues like that I give clear instructions in comments section. E.g. Joe please do your part and then assign the task to Sam. Sam do your part and close the issue. We have history in jira and whoever breaks the rule will be punished :)

Cool, an instrument to make your product higher in google search results. The thing is that we need answers not links.