I am wondering how to add the same work item across multiple boards on Devops.
Each project is different in regard to the work item it contains but some of the projects have the same work items.
I am finding it difficult to get through to the helpdesk as the virtual agent will not accept my question.
I tried researching online but could not find a solution.
Related
I want to use SharePoint lists and workflows to improve some internal processes that our company is currently handling with Excel and email. I have a working user knowledge of SharePoint, but I am not a SharePoint developer.
There are 2 specific questions I've been trying to find a solution for. Having not found an answer after a fair amount of searching, I wonder if I'm not asking the right questions or if perhaps what I'm wanting to do is just more advanced (or not possible?) than I'd hoped.
I'd like to have 2 SharePoint sites in our production environment, but one would be the "dev/test" site and the other would be our "production" site. As we make changes to the lists or workflows over time, I'd like to be able to make the changes in "dev/test" site, and then after we verify the changes somehow move those to the "production" site.
I've looked at the list template, but that seems to only be usable for creating a new list, not updating the columns, views, etc. of an existing list.
Is there a way to move list changes (but not data) from one site to another?
Can the data in specific lists be automatically backed up and restored independently of a full SharePoint server backup?
I am currently working in a SharePoint 2019 Server environment and appreciate any answers or guidance you all can provide.
Thanks!
Problem
I have a gitlab with a lot of old repositories. I want to mention my gitlab as a reference on my CV but I do not want all the old repositories to appear there, just the more relevant ones.
Just making the projects private is not enough as this leaves a lot of clutter in my dashboard and it is hard to see the projects I am trying to showcase.
I do not want to delete the old projects, as I want access to them in the future, I just want to hide them from other people to see that they even exist.
What I Tried
I tried archiving the old projects but they still appear on my Projects lists, just with an archived tag.
I saw mentions of playing with the "Metrics Dashboard" under the visibility settings but this is greyed out for me + I do not think this is what I need from my understanding.
Required Result
For me to be able to choose which projects appear and do not appear in my gitlab dashboard.
Thanks in advance for any help available!
EDIT
I found out that I can star and un-star projects, and that will count as activity on the project without actually changing anything. As the dashboard displays projects by when there was last activity on them then you can actually arrange your project by staring and un-staring the projects in the reverse order you want them to appear.
This somewhat does what I want, but with an ugly work around. Also it will always display 10 projects as far as I can tell, so if I want to only showcase 6 of them the best I can do is push the 4 I don't want to the bottom, but I still can't hide them completely.
This is why I am not writing this as an answer to my question. There has to be a way to just tell a project to be hidden or arrange the projects without this ugly workaround, and if there truly by design isn't a way of doing this then it will also just be good to be officially told that.
GitLab Groups do exactly what you need. See here for more info.
You can assign each project to a different group
You can move a project from one group to another as needed
You can assign different permissions and visibility for each group
You can also create subgroups
Each group/subgroup is treated as a separate namespace, meaning you access it using a different URL
So you can define a public group called yourfullname and a public subgroup called portfolio. Move the projects you want prospective employers to view to the portfolio subgroup and make sure their visibility is also public. All other groups/subgroups should be private. Then people can access your projects by visiting the following URL:
gitlab.com/yourfullname/portfolio
You can still view all of your projects in a single dashboard if you want, or you can view all projects within a group or sub-group by navigating to the desired group URL or dashboard. In the image below, archive and development are private (see the lock icon), but portfolio is public:
I am trying to use "Flow" to automate emails every time a new item is added to a SharePoint discussion board.
This is working fine with all lists, however, it does not do anything when I create a flow for the discussion board. The name of the discussion board does not even come up as an option in the "List" category and if I use the "Documents" option instead of the lists, I am able to choose the correct discussion board, but the alerts do not work.
Discussions are based on the folder content type, with each reply to a parent discussion being an item within that folder.
Flow does not currently support many triggers or operations against folders (including discussion boards) in SharePoint sites, though they've been steadily adding functionality since Flow was introduced.
It's possible that this functionality will be added in the future. You can make suggestions and vote on proposed functionality in Microsoft's "Flow Ideas" community.
background
I've been a religious user for github/zenhub for quite a while. We recently moved our repos to gitlab for many reasons, including free pipelines, security, more flexible groups etc.
Problem
Zenhub is a greasemonkey app that's added to github, one of its features is the scrumboard that's similar to gitlab's native issue board. One of the amazing things about zenhub scrumboard is that it allows you to put many repos on the same board (I recall jira had the same thing).
question
Is there a way to do this on gitlab?
Beside a third-party like kanban.leanlabs.io, recent GitLab releases do integrate a more sophisticated issue management.
See "Announcing The GitLab Issue Board " (presented here)
But it might be limited to only the current repo.
Note that with GitLab 13.6 (November 2020), this is no longer limited to a repository:
Group-level management of project integrations
In GitLab 13.3, we added the ability to enable an integration across an entire instance. With GitLab 13.6, that feature is being expanded to allow integrations to be managed at the group level as well!
Group owners can now add an integration to a group, and that integration will be inherited by all projects under that group. This has the potential for saving massive amounts of time, as many organizations have specific integrations that they want rolled out to every project they create.
A great example of this is using our Jira integration. If you’re using Jira, it’s almost always across the whole company. Some of these companies have thousands of projects and therefore had to configure each and every one of those integrations individually.
With group-level management of project integrations, you can add the integration at each parent group, reducing the amount of configuration required by orders of magnitude!
Read more in our announcement on the GitLab blog.
See Documentation and Epic.
In GitLab issues and merge requests within a group display a collection of issues and merge requests from all projects below them.
And they also have an Issue Board available, which aggregates the issues from the projects within the given group. This is currently not reflected in the documentation, and could be well worth a Pull Request in doc/user/group/index.md and doc/user/project/issue_board.md.
Using this together with group labels and milestones, which also span across all subprojects, you can create the desired board view.
I do use github/zenhub in the past. https://gitboard.co is the zenhub alternative for gitlab. Which shows all your issue and merge request in one simple dashboard across multiple projects.
I'm using Gitlab and I've several projects.
project1;
project2;
project3;
Is it possible to have a common Wiki for these projects?
Every wiki is linked to a project, but there is a workaround:
Go to Settings → Services → External Wiki for your 2nd and 3rd projects and set External wiki URL to the URL of your first project wiki:
Or you can host your own wiki, for example, gollum on your server for the same purpose.
Is it possible to have a common Wiki for these projects?
Yes: (October 2020, 4 years later)
GitLab 13.5 proposes:
Group wikis
For many teams, using GitLab wikis for planning and documentation is a critical part of their workflow. Wikis are so popular that they get over a million views each month on GitLab.com. Despite this popularity, teams have struggled with the limitation that wikis were only available at the project level.
Teams working on multiple projects needed to create separate wikis for each repository, leading to a fragmented experience.
In Gitlab 13.5, we are so excited to bring you group wikis!
With 680 upvotes this was the most upvoted feature in the entire GitLab backlog. While highly requested, making a large project-only feature like wikis available at the group level has been a non-trivial operation. We’ve worked tirelessly over the past year to make it happen and now we can’t wait to get it in your hands and hear your feedback.
Group-level wikis open up tons of possibilities to keep your information at a higher level and accessible to a broader set of people. A few examples of what you can put in your group wikis include team-specific information, coding style guides, and designs for your brand or your company.
We know a lot of folks have been looking forward to this feature and shared their input pre-release. We hope all of you will continue to weigh in now that group wikis are available and we’ve opened up a dedicated issue for your feedback.
See Documentation and Issue.