Comments
-
BTW, the "reopen" scenario is an excellent use case for the Automation + custom field solution as you can leverage on Dashboards to show the frequency of reopens.
-
Hi @Hans Petter Farstad , If this is a company managed project, I would recommend using the resolution field for this purpose. That is, when an issue has moved to "done" the user would be required to add the resolution value - "done" or "refused".
-
You are most welcome. Note that the solution @Klára Zikešová suggests is a reasonable approach if you want every issue to provide a numerical count of the number of days you have "been working" on something. I'm not a huge fan of this solution for your scenario but it can be made to work. It really comes down to how you…
-
Yes indeed a better way
-
jira-cloud-for-excel-official
-
If the field already exists you can simply edit the help text. If it does not exist then create the custom field and edit the help text. You need to have the necessary admin permissions.
-
Not OOTB within the app. You might consider using excel or sheets. There is a Jira extension that allows you to easily run queries. Excel/Sheets will allow you to calculate # of days.
-
Hi @[deleted] , assuming you have Org/Site admin permissions you can get billing details here... settings - billing you should also go to User Management and look for active users. If you feel there is an error please contact Atlassian support and select the Billing option.
-
Hi @Arulselvi Rajaram , OOTB you can use the export feature to export all fields however, for attachments I recommend you will need to look to an addon app.
-
Hi @CatherineP , welcome to the community. this article might help you better understand the macro - https://support.atlassian.com/confluence-cloud/docs/insert-the-chart-macro/ . Once the chart is inserted then the data can be entered in the resulting table.
-
Hi @Jeroen Busselman ,Niet naar mijn begrip. U kunt een schermopname gebruiken en die afdrukken.
-
Some further info that could help.. what-is-an-atlassian-team if you try Premium theses might be helpful... what-are-teams-in-advanced-roadmaps associate-a-team-to-an-issue-source-in-advanced-roadmaps
-
Hi @Reihane hashemi , Plans are available in Premium & Enterprise only. You cannot set the assignee of an issue to a Team. You can associate an issue with a Team. Full disclosure- I do not work with Teams to any extent at this time so my understanding is limited. The feature is rather new and, IMO, the benefits not yet…
-
Hi @Stefan M , I am trying to determine exactly what you are referring to here. You mention "application form field". I am not familiar with that field if indeed you mean that literally. Possibly this is a short text custom field or maybe something else. Some questions for you that may allow me to better assist you... * is…
-
Hi @Tata Tatkhashvili , I assume by "workers" you mean users that are assigned issues. I don't know of any way of showing a count of assignees in the roadmap. You can see the users that are currently assigned issues in the roadmap view by looking at the avatars at the top. Regarding the second question I'm not exactly sure…
-
Hi @Rafaela Sobral , welcome to the community. an active sprint should display on the Active sprint board. From that board you should be able to complete the sprint. Is this not the case? Could you share a screenshot of what you are seeing?
-
Hi @nishant , I am sure you already have taken care of your migration by now. If not let me know as there is the migration assistance tool that should help. Note Atlassian does not perform the migration as this is left to the Org admin.
-
Old post but here is some info that may help others... linking-a-gitlab-or-gitlab-self-managed-repository-with-jira
-
Doing a bit of cleanup on all posts here… there's no way to do this to the best of my understanding. If anyone has found such a method please do share it here.
-
No that is not the case AFAIK
-
Hi @Stuart Zahn , Old post. I am wondering if cause was found and the resolution?
-
you cannot ootb
-
hi @Raja Jeevan Kumar Maduri , What exactly have you tried? It seems to me like creating a dashboard with properly formed filters might meet your needs. However your exact goal is not clear at the moment.
-
Assuming you are the Org admin I would refer you to Atlassian support.
-
consider using Groups. Add the user to the 'contractor-grp'. Use the group in your filter, e.g. assignee in membersOf("contractor-grp")
-
Can you remove the last bit of your filter. I suspect there in lies the error. Try the below as a test. project = GTS AND status in (Closed, Completed, Declined, Done, Failed, Resolved) AND resolved >= -1w
-
Yes indeed thank you for confirming that this is a customer. As mentioned above all customers have the ability to view and open issues. There is an open issue or suggestion on this matter you may wish to vote and watch this issue. JSDCLOUD-6983 Ability to restrict customer access
-
Hi @Dariusz Koryzna , welcome to the community. Maybe you could share a screenshot of what you are experiencing. Keep in mind that there are two statuses currently for Epics. There is the issue status that all issues have and then there is the epic status which is unique to Epics. Note that I believe this behavior is going…
-
Hi @Nonla KONE , you need to be the Org admin. You should have the migrate option under the "Import and Export" section in side bar.
-
Hi @Zbyněk Hostaš , welcome to the Community. Are you referring to a Customer? If so then no, customers always have the ability to open tickets.